Bug#928631: Question
Can I confirm that this is a problem with AMD graphics only--or will this affect all systems regardless of Video card type?
Bug#900248: nvidia-driver:update to 390.59 breaks direct rendering
I let things sit overnight so I could come at this again from a fresh angle...right now my main & backup systems are down. For some reason, when I rebooted after the edit to the config file, I lost the link to /etc/alternatives, not sure why. Taking a break to do work around home - then I will re-establish all the links & try again. -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com debianmainuser at http://forums.debian.net
Bug#900248: nvidia-driver: update to 390.59 breaks direct rendering
Well---I'm still picking up the pieces here. Not sure what happened, but that did not work for me & for some reason, I can't revert it back or boot the older 4.16-1. everything just hangs. I'm in my backup system, looking at the kernel logs. Last entry starts: Jun 23 21:22:52 debian kernel: [0.00] Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-23)) #1 SMP Debian 4.16.16-2 (2018-06-22) Jun 23 21:22:52 debian kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-2-amd64 root=UUID=c18c39f1-0e2c-4c89-a534-e3c8414bb273 ro cgroup_enable=memory swapaccount=1 elevator=noop nvidia-current.NVreg_EnablePCIeGen3=1 slab_common.usercopy_fallback=y Normal boot until GDM "should" come up, then I get: Jun 23 21:23:00 debian kernel: [ 28.992343] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 242 Jun 23 21:23:00 debian kernel: [ 29.383969] resource sanity check: requesting [mem 0x000c-0x000f], which spans more than PCI Bus :00 [mem 0x000c-0x000d window] Jun 23 21:23:00 debian kernel: [ 29.384003] caller _nv001169rm+0xe3/0x1d0 [nvidia] mapping multiple BARs Jun 23 21:23:02 debian kernel: [ 30.747951] show_signal_msg: 14 callbacks suppressed Jun 23 21:23:02 debian kernel: [ 30.747953] gnome-shell[1370]: segfault at 20 ip 7f2ee7714aed sp 7fff4654cb00 error 4 in libmutter-2.so.0.0.0[7f2ee7617000+165000] Last line repeats about 50 times with slightly different addresses [7f2ee7617000+165000] is a typical example--the 165000 stays constant. There is also a note about updating runlevels during this period. I get the same result with my older 4.16-1 kernel now...no combination of workaround(s) seem to have any effect. Thoughts welcome.
Bug#900248: nvidia-driver: update to 390.59 breaks direct rendering
I can also confirm that: slab_common.usercopy_fallback=y works for 4-16-2. I have: /etc/nvidia/current/nvidia-drm-outputclass.conf with this content: Section "OutputClass" Identifier "nvidia" MatchDriver"nvidia-drm" Driver "nvidia" ModulePath "/usr/lib/xorg/modules/linux" EndSection also set in my system. I have looked at the nVidia bug report & it "seems" that according to one user: It seems to be fixed on 396.24. [1.040981] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 396.24 Thu Apr 26 00:10:09 PDT 2018 (using threaded interrupts) [1.041976] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 396.24 Wed Apr 25 23:54:18 PDT 2018 [1.049701] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 243 [1.050203] Linux agpgart interface v0.103 [1.058829] [drm] [nvidia-drm] [GPU ID 0x0100] Loading driver Kernel 4.16.8-1
Bug#900248: update to 390.59 breaks direct rendering
Yes--I've got the "black screen" upon update to 4.16-2 also. Have reverted to 4.16-1 until this latest "fupa" is foundVery willing to test options if you have them...am back on the "first fix"--the config went out the door with the kernel update--only the creating an alias works right now. A side note: took 4 minutes of grinding to get to desktop...mutiple GDM errors before it "took". Error: pam_systemd(gdm-launch-environment:session): Failed to create session: Start job for unit user@116.service failed with 'dependency'-pam_systemd(gdm-launch-environment:session): Failed to create session: Start job for unit user@116.service failed with 'failed'pam_systemd(gdm-launch-environment:session): Failed to create session: Start job for unit user-116.slice failed with 'canceled' These 3 messages repeat about 400 times.
Bug#900248: nvidia.conf "fix"
Yes--In my case, the added nvidia.conf works. Reverted everything to "stock", added the nvidia.conf in the recommended location & rebooted. Looks good. -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#900248: Direct Rendering problem
I must add that the upgrade to Xserver 1.20 was at the same time as the Nvidia upgrade & the problem occurred right afterward (the xserver upgrade was blocked until there was a xserver-xorg-video-nvidia package available). Looking at the commit in question, I see that the Xserver is no longer looking for /linux--the location that Nvidia installs its version of libgxl.so. After creating a link from /linux to /extensions to make the nvidia driver work correctly "tends" to make me think that the root cause has been found. I am very open to exploring other options & will help in anything asked. -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#900248: Direct Render problem
Yes---the change in xorg caused the problem. I linked the nvidia libglx.so from /usr/lib/xorg/modules/linux/ to /usr/lib/xorg/modules/extensions/ (renamed the libglx.so in /extensions to libglx.so.bak). Restarted my system & now have direct rendering. dean@debian:~$ glxinfo | grep OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 960/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 390.59 OpenGL core profile shading language version string: 4.60 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.6.0 NVIDIA 390.59 OpenGL shading language version string: 4.60 NVIDIA OpenGL context flags: (none) OpenGL profile mask: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.59 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: That is a "temporary" fix that works.
Bug#900248: Direct Render problem
Greetingstwo more of us have commented on this bug. I have a fully updated install & am experiencing this problem (nothing pinned). I have posted the nvidia-bug-report via a google drive link in the bug report. Still running 390.59-1, the system works with no GL apps working properly. Cairo Dock shows artifacts during animations. GLXGears looks "normal" (several 100fps low). My baseline game (Linux version of UT2004) runs at about 10~15fps. All newer games run about 1~2fps. I have not reverted back--am able to test if more information is needed. -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#900248: More Information
I did not have: [REMOVE] libgles1-glvnd-nvidia:amd64 390.48-3 [REMOVE] libgles1-glvnd-nvidia:i386 390.48-3 in my upgrade to 390.59. Upgrade: xserver-xorg-video-vesa:amd64 (1:2.3.4-1+b2, 1:2.3.4-1+b3), libcuda1-i386:i386 (390.48-3, 390.59-1), libgles-nvidia2:amd64 (390.48-3, 390.59-1), libgles-nvidia2:i386 (390.48-3, 390.59-1), libnvidia-ml1:amd64 (390.48-3, 390.59-1), nvidia-vulkan-icd:amd64 (390.48-3, 390.59-1), nvidia-vulkan-icd:i386 (390.48-3, 390.59-1), nvidia-driver-libs-i386:i386 (390.48-3, 390.59-1), xserver-xorg-core:amd64 (2:1.19.6-1, 2:1.20.0-2), nvidia-egl-icd:amd64 (390.48-3, 390.59-1), nvidia-egl-icd:i386 (390.48-3, 390.59-1), nvidia-driver:amd64 (390.48-3, 390.59-1), xserver-xorg-video-fbdev:amd64 (1:0.4.4-1+b5, 1:0.4.4-1+b6), nvidia-vulkan-common:amd64 (390.48-3, 390.59-1), nvidia-vdpau-driver:amd64 (390.48-3, 390.59-1), libgl1-nvidia-glvnd-glx:amd64 (390.48-3, 390.59-1), libgl1-nvidia-glvnd-glx:i386 (390.48-3, 390.59-1), libglx-nvidia0:amd64 (390.48-3, 390.59-1), libglx-nvidia0:i386 (390.48-3, 390.59-1), nvidia-smi:amd64 (390.48-3, 390.59-1), libnvidia-egl-wayland1:amd64 (390.48-3, 390.59-1), libnvidia-egl-wayland1:i386 (390.48-3, 390.59-1), nvidia-detect:amd64 (390.48-3, 390.59-1), nvidia-kernel-dkms:amd64 (390.48-3, 390.59-1), libegl-nvidia0:amd64 (390.48-3, 390.59-1), libegl-nvidia0:i386 (390.48-3, 390.59-1), nvidia-egl-common:amd64 (390.48-3, 390.59-1), libnvidia-ptxjitcompiler1:amd64 (390.48-3, 390.59-1), libnvidia-ptxjitcompiler1:i386 (390.48-3, 390.59-1), libnvidia-cfg1:amd64 (390.48-3, 390.59-1), libnvidia-cfg1:i386 (390.48-3, 390.59-1), nvidia-legacy-check:amd64 (390.48-3, 390.59-1), nvidia-opencl-common:amd64 (390.48-3, 390.59-1), nvidia-egl-wayland-icd:amd64 (390.48-3, 390.59-1), nvidia-egl-wayland-icd:i386 (390.48-3, 390.59-1), libnvidia-fatbinaryloader:amd64 (390.48-3, 390.59-1), libnvidia-fatbinaryloader:i386 (390.48-3, 390.59-1), nvidia-kernel-support:amd64 (390.48-3, 390.59-1), libnvidia-compiler:amd64 (390.48-3, 390.59-1), nvidia-driver-libs:amd64 (390.48-3, 390.59-1), nvidia-driver-libs:i386 (390.48-3, 390.59-1), nvidia-driver-bin:amd64 (390.48-3, 390.59-1), xserver-xorg-video-nvidia:amd64 (390.48-3, 390.59-1), libcuda1:amd64 (390.48-3, 390.59-1), libcuda1:i386 (390.48-3, 390.59-1), nvidia-egl-wayland-common:amd64 (390.48-3, 390.59-1), libnvidia-glcore:amd64 (390.48-3, 390.59-1), libnvidia-glcore:i386 (390.48-3, 390.59-1), libnvidia-eglcore:amd64 (390.48-3, 390.59-1), libnvidia-eglcore:i386 (390.48-3, 390.59-1), libxslt1.1:amd64 (1.1.32-1, 1.1.32-2), libxslt1.1:i386 (1.1.32-1, 1.1.32-2), nvidia-opencl-icd:amd64 (390.48-3, 390.59-1), nvidia-alternative:amd64 (390.48-3, 390.59-1) End-Date: 2018-05-26 19:58:51 I also have a Google Drive link to the nvidia-bug-report.log nvidia-bug-report.log <https://drive.google.com/file/d/16pGyYAjP88a8KAKCPTSbko40L2QgykWb/view?usp=drive_web> I am still running 390.59, so am ready to try changes -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com dean@debian:~$ glxgears 3755 frames in 5.0 seconds = 750.255 FPS 4040 frames in 5.0 seconds = 807.917 FPS 4306 frames in 5.0 seconds = 860.307 FPS 4284 frames in 5.0 seconds = 856.658 FPS 4281 frames in 5.0 seconds = 856.183 FPS 4300 frames in 5.0 seconds = 859.959 FPS XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1" after 79675 requests (79673 known processed) with 0 events remaining.
Bug#900248: nvidia-driver: update to 390.59 breaks direct rendering
I am also having this issue. dean@debian:~$ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.4 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 18.0.4 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.4 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: Running the most current kernel--had no problems until the update to 390.59-1
Bug#874693: Is this still an issue?
I see that gjs 1.50 has been released. Is this bug still applicable?
Bug#756941: gnome-shell: Gnome-Shell 3.13-1 hangs at GDM
Package: gnome-shell Version: 3.13.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installed then rebooted-Desktop hangs just before GDM login screen. * What exactly did you do (or not do) that was effective (or ineffective)? Tried to reinstall again. * What was the outcome of this action? Hang just before GDM login. * What outcome did you expect instead? Login screen I looked at the logs see that Gnome-session should be updated also. I have downgraded to 3.12 to use the desktop am waiting to see session before trying 3.13 again. -- System Information: Debian Release: jessie/sid APT prefers experimental APT policy: (900, 'experimental'), (900, 'unstable'), (850, 'testing'), (500, 'testing-updates'), (500, 'testing-proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-rc6-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.20.0-2 ii evolution-data-server3.12.2-1 ii gconf-gsettings-backend [gsettings-backend] 3.2.6-2 ii gir1.2-accountsservice-1.0 0.6.37-3 ii gir1.2-atspi-2.0 2.12.0-2 ii gir1.2-caribou-1.0 0.4.13-1 ii gir1.2-clutter-1.0 1.18.2-2 ii gir1.2-freedesktop 1.40.0-2 ii gir1.2-gcr-3 3.12.2-1 ii gir1.2-gdesktopenums-3.0 3.13.2-1 ii gir1.2-gdm3 3.12.2-3 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.40.0-2 ii gir1.2-gmenu-3.0 3.10.1-1 ii gir1.2-gnomebluetooth-1.03.12.0-5 ii gir1.2-gnomedesktop-3.0 3.12.2-2 ii gir1.2-gtk-3.0 3.12.2-1+b1 ii gir1.2-ibus-1.0 1.5.7-2 ii gir1.2-mutter-3.03.13.1-1 ii gir1.2-networkmanager-1.00.9.10.0-1 ii gir1.2-nmgtk-1.0 0.9.10.0-2 ii gir1.2-pango-1.0 1.36.3-1 ii gir1.2-polkit-1.00.112-2 ii gir1.2-soup-2.4 2.46.0-2 ii gir1.2-telepathyglib-0.120.24.0-1 ii gir1.2-telepathylogger-0.2 0.8.0-3 ii gir1.2-upowerglib-1.00.99.0-3 ii gjs 1.40.1-2 ii gnome-icon-theme-symbolic3.12.0-1 ii gnome-settings-daemon3.12.2-1 ii gnome-shell-common 3.13.1-1 ii gnome-themes-standard3.12.0-1 ii gsettings-desktop-schemas3.13.2-1 ii libatk-bridge2.0-0 2.12.1-1+b1 ii libatk1.0-0 2.12.0-1 ii libc62.19-7 ii libcairo21.12.16-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libclutter-1.0-0 1.18.2-2 ii libcogl-pango20 1.18.2-1 ii libcogl201.18.2-1 ii libcroco30.6.8-2 ii libdbus-glib-1-2 0.102-1 ii libecal-1.2-16 3.12.2-1 ii libedataserver-1.2-183.12.2-1 ii libgcr-base-3-1 3.12.2-1 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libgirepository-1.0-11.40.0-2 ii libgjs0e [libgjs0-libmozjs-24-0] 1.40.1-2 ii libglib2.0-0 2.41.1-2 ii libgstreamer1.0-01.4.0-1 ii libgtk-3-0 3.12.2-1+b1 ii libical1 1.0-1 ii libjson-glib-1.0-0 1.0.2-1 ii libmozjs-24-024.2.0-2 ii libmutter0d 3.13.1-1 ii libnm-glib4 0.9.10.0-1 ii libnm-util2 0.9.10.0-1 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii libpolkit-agent-1-0 0.112-2 ii libpolkit-gobject-1-00.112-2 ii libpulse-mainloop-glib0 5.0-4 ii libpulse05.0-4 ii libsecret-1-00.18-1 ii
Bug#746205: Not sure what update cured problem...
Not sure what update cured problem, but log is now working normal...running a experimental sourced install had about 20/25 updates this morning If the problem comes back I will post more. -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#746205: gnome-system-log will freeze for several minutes with 100% cpu useage.
Package: gnome-system-log Version: 3.9.90-2 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Running Gnome-System-Log after 3.12 Gnome update. * What exactly did you do (or not do) that was effective (or ineffective)? found all common depends for programs that are running slow on my system-GDM3, Synaptic Gnome-System-Log. reinstalled all depends then ran Synaptic Gnome-System-Log from the terminal. * What was the outcome of this action? No interesting output from running Synaptic from the terminal, but Gnome- System-Log produced repeating output: (gnome-system-log:8731): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed (gnome-system-log:8731): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed (gnome-system-log:8731): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed (gnome-system-log:8731): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed As long as the cursor was in the Gnome-System-Log window was moved. * What outcome did you expect instead? That Gnome-System-Log would work normally not use 100% of the cpu. *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers experimental APT policy: (900, 'experimental'), (900, 'unstable'), (850, 'testing'), (500, 'testing-updates'), (500, 'testing-proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-system-log depends on: ii dconf-gsettings-backend [gsettings-backend] 0.20.0-2 ii gconf-gsettings-backend [gsettings-backend] 3.2.6-2 ii gsettings-desktop-schemas3.12.0-1 ii libatk1.0-0 2.12.0-1 ii libc62.18-4 ii libcairo-gobject21.12.16-2 ii libcairo21.12.16-2 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-3 ii libgtk-3-0 3.12.1-1 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii policykit-1 0.112-2 ii zlib1g 1:1.2.8.dfsg-1 gnome-system-log recommends no packages. Versions of packages gnome-system-log suggests: ii yelp 3.12.0-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721630: apt-listbugs: With the upgrade to Ruby 1.9 in Sid, apt-listbugs no longer works.
Package: apt-listbugs Version: 0.1.9 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** * Upgrade to Ruby 1.9 in Sid * removed 10apt-listbugs from apt.conf.d to allow the upgrade. * /usr/lib/ruby/vendor_ruby/gettext/mo.rb:46: undefined method `force_encoding' for \225\004\022\336:String (NoMethodError) from /usr/lib/ruby/vendor_ruby/gettext/text_domain.rb:16:in `require' from /usr/lib/ruby/vendor_ruby/gettext/text_domain.rb:16 from /usr/lib/ruby/vendor_ruby/gettext/text_domain_manager.rb:14:in `require' from /usr/lib/ruby/vendor_ruby/gettext/text_domain_manager.rb:14 from /usr/lib/ruby/vendor_ruby/gettext.rb:19:in `require' from /usr/lib/ruby/vendor_ruby/gettext.rb:19 from /usr/sbin/apt-listbugs:274:in `require' from /usr/sbin/apt-listbugs:274 E: Sub-process /usr/sbin/apt-listbugs apt || exit 10 returned an error code (10) E: Failure running script /usr/sbin/apt-listbugs apt || exit 10 A package failed to install. Trying to recover: * What outcome did you expect instead? apt-listbugs to list problems. *** End of the template - remove these lines *** -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (900, 'unstable'), (850, 'testing'), (500, 'testing-proposed-updates'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apt-listbugs depends on: ii apt 0.9.11.2 ii libruby1.8 1.8.7.358-7.1 ii ruby-debian 0.3.8+b1 ii ruby-gettext 3.0.0-1 ii ruby-httpclient 2.3.3-2 ii ruby-xmlparser 0.7.2-2 ii ruby1.8 1.8.7.358-7.1 apt-listbugs recommends no packages. Versions of packages apt-listbugs suggests: ii debianutils 4.4 ii google-chrome-unstable [www-browser] 31.0.1612.0-1 ii iceweasel [www-browser] 25.0~a2+20130830004004-1 ii opera-next [www-browser] 12.16.1860 ii reportbug 6.4.4 ii w3m [www-browser] 0.5.3-11 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721574: Thanks for the Fix!!
I thank both you and Francesco for fixing listbugs so quickly!!! Again, Thank You! -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#678473: gdm3: I upgraded to the new version of GDM3-3.4.1 and the xserver would not start. had to downgrade to old version of GDM3
Package: gdm3 Version: 3.0.4-4 Severity: critical Justification: breaks the whole system Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Normal upgrade installing new version of GDM3 * What exactly did you do (or not do) that was effective (or ineffective)? Tried to login several times use startx to get system to goto graphical login. * What was the outcome of this action? Text-only login. * What outcome did you expect instead? Graphical login. *** End of the template - remove these lines *** -- System Information: Debian Release: Experimental APT prefers experimental APT policy: (950, 'experimental'), (900, 'unstable'), (875, 'testing'), (850, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.4-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdm3 depends on: ii accountsservice 0.6.21-4 ii adduser 3.113+nmu3 ii dconf-gsettings-backend 0.12.1-2 ii debconf [debconf-2.0] 1.5.44 ii gconf23.2.5-1 ii gnome-session [x-session 3.4.2.1-1 ii gnome-session-bin 3.4.2.1-1 ii gnome-session-fallback [ 3.4.2.1-1 ii gnome-terminal [x-termin 3.4.1.1-1 ii gsettings-desktop-schema 3.4.2-1 ii libaccountsservice0 0.6.21-4 ii libatk1.0-0 2.4.0-2 ii libattr1 1:2.4.46-8 ii libaudit0 1:1.7.18-1.1 ii libc6 2.15-0ubuntu10 ii libcairo-gobject2 1.12.2-2 ii libcairo2 1.12.2-2 ii libcanberra-gtk3-00.28-4 ii libcanberra0 0.28-4 ii libdbus-1-3 1.6.0-1 ii libdbus-glib-1-2 0.98-1 ii libfontconfig12.9.0-6 ii libfreetype6 2.4.9-1 ii libgconf2-4 3.2.5-1 ii libgdk-pixbuf2.0-02.26.1-1 ii libglib2.0-0 2.33.2-1 ii libglib2.0-bin2.33.2-1 ii libgtk-3-03.4.2-1 ii libpam-modules1.1.3-7.1 ii libpam-runtime1.1.3-7.1 ii libpam0g 1.1.3-7.1 ii libpango1.0-0 1.30.0-1 ii librsvg2-common 2.36.1-1 ii libselinux1 2.1.9-5 ii libupower-glib1 0.9.16-3 ii libwrap0 7.6.q-23 ii libx11-6 2:1.5.0-1 ii libxau6 1:1.0.7-1 ii libxdmcp6 1:1.1.1-1 ii libxklavier16 5.2.1-1 ii libxrandr22:1.3.2-2 ii lsb-base 4.1+Debian7 ii metacity [x-window-manag 1:2.34.3-2 ii mutter [x-window-manager 3.4.1+git20120502.4148a5cc-0ubuntu1~12.04~ricotz0 ii policykit-1-gnome 0.105-2 ii upower0.9.16-3 Versions of packages gdm3 recommends: ii at-spi 1.32.0-1 ii desktop-base 6.0.7 ii gnome-icon-theme 3.4.0-0ubuntu1 ii gnome-power-manager3.4.0-2 ii gnome-settings-daemon 3.4.2-3 ii x11-xkb-utils 7.7~1 pn xserver-xephyr none ii xserver-xorg 1:7.6+13 ii zenity 3.4.0-2 Versions of packages gdm3 suggests: ii gnome-mag 1:0.16.3-1 pn gnome-orcanone pn gok none ii libpam-gnome-keyring 3.4.1-4 ii metacity 1:2.34.3-2 -- Configuration Files: /etc/gdm3/daemon.conf changed: [daemon] TimedLoginEnable=true AutomaticLoginEnable=false TimedLogin=dean AutomaticLogin=dean TimedLoginDelay=30 [security] [xdmcp] [greeter] [chooser] [debug] -- debconf information: * shared/default-x-display-manager: gdm3 gdm3/daemon_name: /usr/sbin/gdm3 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669949: Another clue---
I looked at my /var the folder that was /var/run is now a symlinkSo we might look to see if the script looks for /var/run if it's not a symlink--creates it That would have caused all kinds of havoc in my system with a symlink trying to point at a symlink I was on the LinuxmintDebian forum this morning another old install had fallen to the same problem...he restored to a prior state instead of looking for the problem. I posted the fix in the Sid Testing breakage update threadI wonder if anyone in Aptosid has seen this? -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#669949: Hmmmm---
OK--that makes sense...I'm running the newest kernel--3.3 trunk. I'll try a older kernel first, as it's the easiest in the list. I think I'll do a line-by-line between 22.1 24 to really get a feel for the differences--everytime I revert to 22.1 the problem goes away... Quick question: are there any mounts that changes between 22.1 24? My system has been running for over a year now I normally take the existing config instead of the developer version. That leads me to the thought that by the time it gets to Testing there may be more reports--people that default to N during updates have long-standing installs -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#669949: Results of Test #1
Negative result with using the 3.2.0-2 kernel (3.2.16-1)--same as 3.3.0-trunk (3.3.4-1)..I've got some work to do around the house, so I'll be working on this problem this evening..I think that I will do a line-by-line next--will post if I find anything there. If not--I'll do the single-user mode go from there...Wish me luck -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#669949: Found the problem script....
The problem in my case is /lib/init/mount-functions.sh as soon as I used the script from 22.1 all functions were normal again--looking at mount-functions.sh--there are lots of changes--I'm having a hard time pinpointing exactly where the culprit is... My best guess is something is being mounted in the wrong location for my system...Looking forward to your take on this. -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com mount-functions-22.1.sh Description: Bourne shell script mount-functions-24.sh Description: Bourne shell script
Bug#669949: Found the answer
Found it---In my system /run was a symlink to /var/run--So my guess is that the mount script was going crazy giving up...I remember about a year or so ago there was a problem with /var/run /run the fix was linking /run to /var/runI wonder how many systems are still running this way. I recreated the /run folder populated it with the contents of /var/run now things work as expected... Interesting little puzzle--glad to have found the answer. -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#669949: Tried the exit 0
Tried exit 0 to no effect--still had to reload my USB devices restart ALSA for my soundcard to work. What would you like me to try next? -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#669949: mouse, keyboard sound not working in -24
I'm almost on the way to work (7am my time)...I'll copy the -22.1 bootlog this evening then upgrade to -24 again--copy the bootlog--and then try the exit0...I reboot after every major change to the main system..so the devices do not show up afterwards. Do you want my system specs also? On Wed, May 09, 2012 at 06:52:52PM -0700, Dean Loros wrote: It looks like this is not fixed in my case. I yes'd all developer changes to Initscripts (thought that might fix things), but I still have no keyboard or mouse--using both as USB3 devices. I can unplug replug them--then both will work normally. What logs do you need to see this? I also have downgraded before this to 22.1 have had normal functions...I don't know if I can downgrade easily with the current version. Only things that seem to be affected are the keyboard mouse. This is odd. It's definitely fixed the problem for myself, which was due to cleaning /run and removing some of the udev state. If you add an exit 0 to the top of /lib/init/bootclean.sh (to disable cleaning), does this prevent the problem? Did you reboot after installing -24? (Since this is a problem which is created at boot) It would be useful to have a copy of the boot logs for 22.1 and 24 so that we can look at any obvious differences. Thanks, Roger -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#669949: found sound problem....
I found that doing alsa force-reload brought my sound card back...so what is turning off Alsa? -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#669949: Still having a problem with no keyboard mouse after upgrade to .24
It looks like this is not fixed in my case. I yes'd all developer changes to Initscripts (thought that might fix things), but I still have no keyboard or mouse--using both as USB3 devices. I can unplug replug them--then both will work normally. What logs do you need to see this? I also have downgraded before this to 22.1 have had normal functions...I don't know if I can downgrade easily with the current version. Only things that seem to be affected are the keyboard mouse. -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#669949: More information.
I can also verify that I have no sound with -24 reverting to -22.1 I have sound again. the downgrade was messy due to bootlogd. Looking at -24, I see that many things are changed in mountlocation. I also note that during a verbose boot I get modprobe information with -22.1 don't get the same info. -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#669949: Further information.
I can also verify that I have no sound with -24 reverting to -22.1 I have sound again. The downgrade was messy due to bootlogd. Looking at -24, I see that many things are changed in mount location. I also note that during a verbose boot I get modprobe information with -22.1 don't get the same info with -24. Could it be that devices that need to be probed are not being mounted/probed/made available to the system? (Edited with more information clarified) -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#641509: shotwell: Shotwell starts, but crashes after main window opens
Package: shotwell Version: 0.11.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropiate *** * What led up to the situation? Trying to start Shotwell * What exactly did you do (or not do) that was effective (or ineffective)? Ran in terminal to see errors * What was the outcome of this action? Error output * What outcome did you expect instead? Program start Terminal output follows: shotwell ** (process:28128): DEBUG: GConfEngine.vala:191: Converting GConf settings to gsettings... ** (process:28128): DEBUG: GConfEngine.vala:205: GConf to gsettings conversion completed *** glibc detected *** shotwell: double free or corruption (fasttop): 0x03e3ba40 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x72606)[0x7fbc17e73606] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x6c)[0x7fbc17e7833c] /usr/lib/libgexiv2.so.0(gexiv2_metadata_get_exif_tag_string+0x1f1)[0x7fbc1f367051] shotwell(photo_metadata_get_string+0x64)[0x4bd444] shotwell(photo_metadata_get_date_time+0x94)[0x4bd744] shotwell(photo_metadata_get_first_date_time+0x96)[0x4bd8b6] shotwell(photo_prepare_for_reimport_master+0x34a)[0x5d7a6a] shotwell[0x6b4803] shotwell[0x488588] /lib/libglib-2.0.so.0(+0x6cf60)[0x7fbc18bb4f60] /lib/libglib-2.0.so.0(+0x6a984)[0x7fbc18bb2984] /lib/x86_64-linux-gnu/libpthread.so.0(+0x6b40)[0x7fbc1818bb40] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fbc17ed636d] === Memory map: 0040-007c2000 r-xp 08:11 264219 /usr/bin/shotwell 009c2000-009d9000 rw-p 003c2000 08:11 264219 /usr/bin/shotwell 009d9000-009dc000 rw-p 00:00 0 00aa7000-03f74000 rw-p 00:00 0 [heap] 7fbbe800-7fbbe82a1000 rw-p 00:00 0 7fbbe82a1000-7fbbec00 ---p 00:00 0 7fbbf000-7fbbf02c2000 rw-p 00:00 0 7fbbf02c2000-7fbbf400 ---p 00:00 0 7fbbf67fd000-7fbbf67fe000 ---p 00:00 0 7fbbf67fe000-7fbbf6ffe000 rw-p 00:00 0 7fbbf6ffe000-7fbbf6fff000 ---p 00:00 0 7fbbf6fff000-7fbbf77ff000 rw-p 00:00 0 7fbbf77ff000-7fbbf780 ---p 00:00 0 7fbbf780-7fbbf800 rw-p 00:00 0 7fbbf800-7fbbf8505000 rw-p 00:00 0 7fbbf8505000-7fbbfc00 ---p 00:00 0 7fbbfc34b000-7fbbfc34c000 ---p 00:00 0 7fbbfc34c000-7fbbfcb4c000 rw-p 00:00 0 7fbbfcb4c000-7fbbfcb4d000 ---p 00:00 0 7fbbfcb4d000-7fbbfd34d000 rw-p 00:00 0 7fbbfd34d000-7fbbfd67e000 rw-p 00:00 0 7fbbfd854000-7fbbfd8b4000 rw-s 00:04 2326540 /SYSV (deleted) 7fbbfd8b4000-7fbbfd8b8000 r-xp 08:11 3281870 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so 7fbbfd8b8000-7fbbfdab8000 ---p 4000 08:11 3281870 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so 7fbbfdab8000-7fbbfdab9000 rw-p 4000 08:11 3281870 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so 7fbbfdab9000-7fbbfdaba000 ---p 00:00 0 7fbbfdaba000-7fbbfe2ba000 rw-p 00:00 0 7fbbfe2ba000-7fbbfe2ce000 r-xp 08:11 272109 /usr/lib/gio/modules/libgioremote-volume-monitor.so 7fbbfe2ce000-7fbbfe4ce000 ---p 00014000 08:11 272109 /usr/lib/gio/modules/libgioremote-volume-monitor.so 7fbbfe4ce000-7fbbfe4cf000 rw-p 00014000 08:11 272109 /usr/lib/gio/modules/libgioremote-volume-monitor.so 7fbbfe4cf000-7fbbfe565000 r--p 08:11 1181101 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-Oblique.ttf 7fbbfe565000-7fbbfe5fb000 r--p 08:11 1181108 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-BoldOblique.ttf 7fbbfe5fb000-7fbbfe5fd000 r-xp 08:11 526825 /usr/lib/x86_64-linux-gnu/pango/1.6.0/modules/pango-basic-fc.so 7fbbfe5fd000-7fbbfe7fc000 ---p 2000 08:11 526825 /usr/lib/x86_64-linux-gnu/pango/1.6.0/modules/pango-basic-fc.so 7fbbfe7fc000-7fbbfe7fd000 rw-p 1000 08:11 526825 /usr/lib/x86_64-linux-gnu/pango/1.6.0/modules/pango-basic-fc.so 7fbbfe7fd000-7fbbfe7fe000 ---p 00:00 0 7fbbfe7fe000-7fbbfeffe000 rw-p 00:00 0 7fbbfeffe000-7fbbfefff000 ---p 00:00 0 7fbbfefff000-7fbbff7ff000 rw-p 00:00 0 7fbbff7ff000-7fbbff80 ---p 00:00 0 7fbbff80-7fbc rw-p 00:00 0 7fbc-7fbc002c6000 rw-p 00:00 0 7fbc002c6000-7fbc0400 ---p 00:00 0 7fbc04028000-7fbc04088000 rw-s 00:04 2293771 /SYSV (deleted) 7fbc04088000-7fbc04089000 r--s 08:11 1840642 /var/cache/fontconfig/c05880de57d1f5e948fdfacc138775d9-le64.cache-3 7fbc04089000-7fbc04092000 r--s 08:11 1840641 /var/cache/fontconfig/945677eb7aeaf62f1d50efc3fb3ec7d8-le64.cache-3 7fbc04092000-7fbc04094000 r--s 08:11 1840565 /var/cache/fontconfig/99e8ed0e538f840c565b6ed5dad60d56-le64.cache-3 7fbc04094000-7fbc04095000 r--s 08:11 1840560 /var/cache/fontconfig/32d4f95bd5d69a78cf8aaeeec87c8f3f-le64.cache-3
Bug#640467: Acknowledgement (gnome-tweak-tool: Will not start due to undefined symbol: g_callable_info_skip_return)
Unfortunately there is not a version in unstable :( I went to http://ftp.gnome.org/pub/GNOME/sources/gnome-tweak-tool/ and built versions 3.04.1---every build failed to start with the same error I reported at first. Should I report this error upstream or wait for a python fix here? On Mon, Sep 5, 2011 at 1:05 PM, Josselin Mouette j...@debian.org wrote: reassign 640647 python-gobject 2.90.3-1 retitle 640647 Insufficient requirement on glib thanks Le lundi 05 septembre 2011 à 08:09 -0700, Dean Loros a écrit : (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: g_callable_info_skip_return Looks like a too low build-dependency in pygobject (and the required glib is not available anyway). Downgrading this package to the version in unstable should restore the functionality. Cheers, -- .''`. Josselin Mouette : :' : `. `' `- -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#640467: Acknowledgement (gnome-tweak-tool: Will not start due to undefined symbol: g_callable_info_skip_return)
I just tried that get a ton of errorsdowngraded to python-gobject 2.28.6-4 gnome-tweak-tool Traceback (most recent call last): File /usr/local/bin/gnome-tweak-tool, line 76, in module MainWindow() File /usr/local/lib/python2.6/dist-packages/gtweak/mainwindow.py, line 44, in __init__ model) File /usr/local/lib/python2.6/dist-packages/gtweak/tweakview.py, line 40, in __init__ self._model.load_tweaks() File /usr/local/lib/python2.6/dist-packages/gtweak/tweakmodel.py, line 125, in load_tweaks mods = __import__(gtweak.tweaks, globals(), locals(), tweak_files, 0) File /usr/local/lib/python2.6/dist-packages/gtweak/tweaks/tweak_nautilus.py, line 47, in module DesktopIconTweak(group_name=TWEAK_GROUP_FILE_MANAGER), File /usr/local/lib/python2.6/dist-packages/gtweak/tweaks/tweak_nautilus.py, line 30, in __init__ **options) File /usr/local/lib/python2.6/dist-packages/gtweak/widgets.py, line 107, in __init__ _GSettingsTweak.__init__(self, schema_name, key_name, **options) File /usr/local/lib/python2.6/dist-packages/gtweak/widgets.py, line 99, in __init__ self.settings = GSettingsSetting(schema_name, **options) File /usr/local/lib/python2.6/dist-packages/gtweak/gsettings.py, line 66, in __init__ _SCHEMA_CACHE[schema_name] = _GSettingsSchema(schema_name, **options) File /usr/local/lib/python2.6/dist-packages/gtweak/gsettings.py, line 34, in __init__ assert(os.path.exists(schema_path)) AssertionError So it looks like I'm waiting to make things work.Thank you for the info On Sun, Sep 11, 2011 at 2:19 PM, Sam Morris s...@robots.org.uk wrote: On Sun, 2011-09-11 at 11:41 -0700, Dean Loros wrote: Unfortunately there is not a version in unstable :( I went to http://ftp.gnome.org/pub/GNOME/sources/gnome-tweak-tool/ and built versions 3.04.1---every build failed to start with the same error I reported at first. Should I report this error upstream or wait for a python fix here? Try python-gobject from unstable. g-t-t works fine with it for me. -- Sam Morris https://robots.org.uk/ 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#640467: Acknowledgement (gnome-tweak-tool: Will not start due to undefined symbol: g_callable_info_skip_return)
(/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyDict_GetItemString (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyUnicodeUCS4_FromEncodedObject (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyFloat_AsDouble (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyObject_IsTrue (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyArg_ParseTuple (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyNumber_Int (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyDict_New(/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyCallable_Check (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyString_FromFormat (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyDict_Next (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyCObject_AsVoidPtr (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyErr_Fetch (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyMapping_Size (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: _PyObject_New (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyInt_FromLong (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyEval_SaveThread (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyModule_AddObject (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyDict_SetItem (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyObject_Repr (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyNumber_Check (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyLong_AsLongLong (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyType_IsSubtype (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyTuple_Size (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyErr_Format (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyLong_FromLongLong (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: g_callable_info_skip_return (/usr/lib/python2.6/dist-packages/gi/_gi.so) undefined symbol: PyObject_GC_UnTrack (/usr/lib/python2.6/dist-packages/gi/_gi.so) -- Cheers!!! Dean Loros Performance by Design Ltd. autocrosser at http://forums.linuxmint.com
Bug#640467: gnome-tweak-tool: Will not start due to undefined symbol: g_callable_info_skip_return
Package: gnome-tweak-tool Version: 3.0.4-1 Severity: grave Justification: renders package unusable Dear Maintainer, '/usr/bin/gnome-tweak-tool' Traceback (most recent call last): File /usr/bin/gnome-tweak-tool, line 20, in module import gi File /usr/lib/python2.6/dist-packages/gi/__init__.py, line 23, in module from ._gi import _API, Repository ImportError: /usr/lib/python2.6/dist-packages/gi/_gi.so: undefined symbol: g_callable_info_skip_return * What led up to the situation? Update rendered application unusable. * What exactly did you do (or not do) that was effective (or ineffective)? Ran in terminal to see error. * What was the outcome of this action? Output above. * What outcome did you expect instead? Possible start of application. -- System Information: Debian Release: wheezy/sid APT prefers experimental APT policy: (500, 'experimental'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-tweak-tool depends on: ii gnome-shell3.0.2-1+b1 ii gsettings-desktop-schemas 3.0.1-1 ii python 2.6.7-3 ii python2.6 2.6.7-4 ii python2.7 2.7.2-5 gnome-tweak-tool recommends no packages. gnome-tweak-tool suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639611: software-properties-gtk: Software-sources-gtk can't be launched in current Gnome 3.02
Package: software-properties-gtk Version: 0.80.6debian1 Severity: grave Tags: upstream Justification: renders package unusable Trying to launch Software-properties-gtk from within Synaptic or via terminal will not work. Terminal output: sudo software-properties-gtk [sudo] password for dean: /usr/lib/python2.6/dist-packages/gi/overrides/Gtk.py:47: RuntimeWarning: You have imported the Gtk 2.0 module. Because Gtk 2.0 was not designed for use with introspection some of the interfaces and API will fail. As such this is not supported by the pygobject development team and we encourage you to port your app to Gtk 3 or greater. PyGTK is the recomended python module to use with Gtk 2.0 warnings.warn(warn_msg, RuntimeWarning) /usr/lib/python2.6/dist-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed import gobject._gobject WARNING: can not get name for 'CellRendererText object at 0x1d1c2d0 (GtkCellRendererText at 0x1ebf960)' WARNING: can not get name for 'TextBuffer object at 0x1d1cc30 (GtkTextBuffer at 0x1758130)' Traceback (most recent call last): File /usr/bin/software-properties-gtk, line 111, in module app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File /usr/lib/python2.6/dist- packages/softwareproperties/gtk/SoftwarePropertiesGtk.py, line 126, in __init__ self.init_auto_update() File /usr/lib/python2.6/dist- packages/softwareproperties/gtk/SoftwarePropertiesGtk.py, line 193, in init_auto_update gobject.TYPE_INT) File /usr/lib/python2.6/dist-packages/gi/overrides/Gtk.py, line 918, in __init__ self.set_column_types(column_types) File /usr/lib/python2.6/dist-packages/gi/types.py, line 44, in function return info.invoke(*args, **kwargs) TypeError: Item 0: Must be gobject.GType, not gobject.GType -- System Information: Debian Release: wheezy/sid APT prefers experimental APT policy: (500, 'experimental'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages software-properties-gtk depends on: ii gir1.2-gtk-2.0 2.24.5-4 GTK+ graphical user interface libr ii gksu 2.0.2-5 graphical frontend to su ii python 2.6.7-3 interactive high-level object-orie ii python-gobject 2.90.2-1 Python 2.x bindings for gobject-in ii python-software-properties 0.80.6debian1 manage the repositories that you i ii python2.5 2.5.5-11 An interactive high-level object-o ii python2.6 2.6.7-4 An interactive high-level object-o ii synaptic 0.75.2Graphical package manager software-properties-gtk recommends no packages. software-properties-gtk suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
