[Desktop-packages] [Bug 1308105]
I would only suggest to prospective testers to first try out Xfce4-Settings GIT (hence with Olivier's recent fix) with *no patch*. At least here it fixes the issue, and maybe this addresses your concerns, too. -- You received this bug notification because you are a member of Desktop Packages, 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 Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in xfce4-settings package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308105]
Here we go: Bug 11525 BTW, I wonder if this xfsettingsd crash issue was solved by addressing the Coverity scan reports... https://scan.coverity.com/projects/4135 -- You received this bug notification because you are a member of Desktop Packages, 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 Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: Fix Released Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in xfce4-settings package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308105]
As for the xfsettingsd crash, I noticed that with current master I was no longer experiencing the crashes. So I did some GIT bisecting, and it turns out that I can reproduce the crash with: http://git.xfce.org/xfce/xfce4-settings/commit/?id=5a7f55a049147320adb8e2dc8495d6f868c4d6ac But I get no more crashes with: http://git.xfce.org/xfce/xfce4-settings/commit/?id=404d982f2936a58649423642956be563982b2ffa It seems to me that Olivier has inadvertently fixed this issue... Just to confirm, I do NOT get xfsettingsd crashes when using master and my usual test case. As far as my setup is concerned, this issue is fixed. = So what remains to be addressed is the disabled `Mirror displays` option introduced in 835671ad8db9bcaed4ec3d53753b7f9a8b4610a7. Should I open a separate ticket on this issue? -- You received this bug notification because you are a member of Desktop Packages, 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 Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: In Progress Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in xfce4-settings package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308105]
Surprisingly, not. >git checkout master (22206) Already on 'master' Your branch is up-to-date with 'origin/master'. >git checkout master (22206) returned '0' Then: make distclean && ./autogen.sh && make I also removed 'xfce4-settings' from Synaptic. After `make install`, I run `xfsettingsd --replace`. When I plug the HDMI cable, the `Mirror displays` option is disabled. So this issue already seems to be in GIT master. But more strangely, still, I can NOT reproduce the xfsettingsd crash. It's as if it were already fixed in master. Go figure -- You received this bug notification because you are a member of Desktop Packages, 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 Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: In Progress Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in xfce4-settings package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308105]
OK: disabled `Mirror displays` option GIT bisect points me to: >git bisect bad (4) 835671ad8db9bcaed4ec3d53753b7f9a8b4610a7 is the first bad commit commit 835671ad8db9bcaed4ec3d53753b7f9a8b4610a7 Author: Sean Davis Date: Sat Jan 31 11:31:52 2015 -0500 Fix issues found with cppcheck (Thanks Mario) (Bug 10879) :04 04 f3782b2eee70c04f7715a6aa10d8a2ab7b5b3d42 4cbdb493675c1f077dfb1da25cc087eae33f8e3d M dialogs :04 04 995180b85348189b33ae73a4b3a1bd4f2ba675a6 f5e0a19760ca4a33b5ae0e681da7ee0976f5935e M xfsettingsd >git bisect bad (4) returned '0' There was some unexpected impact of this clean-up... -- You received this bug notification because you are a member of Desktop Packages, 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 Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: In Progress Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in xfce4-settings package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308105]
Created attachment 5916 disabled `Mirror displays` option with Sean's updated patch -- You received this bug notification because you are a member of Desktop Packages, 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 Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: In Progress Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in xfce4-settings package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308105]
As far as fixing the issue goes, it's very simple: - if I do `/usr/bin/xfsettingsd --replace` (4.11.3), then I can easily replicate the crash - if I do `/usr/local/bin/xfsettingsd --replace` (GIT master with Sean's updated patch), the I can no longer replicate the crash I think the patch is effective at addressing the issue. As for the disabled `Mirror displays` option, if I remove the stock xfce4-settings and only keep the /usr/local/bin installation, then the issue persists: when I connect the HDMI cable, the `Mirror displays` option is disabled (see attached screenshot). I'm not sure how else to test this... -- You received this bug notification because you are a member of Desktop Packages, 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 Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: In Progress Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in xfce4-settings package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308105]
Thanks a lot André! And thanks a lot for the instructions; although I know most of them individually, stringing them all together wasn't immediately obvious. I've tested Sean's updated patch and I'm happy to report that it seems indeed to solve the `xfsettingsd` crashes. I will test it for a couple more days to make sure that all is OK, but so far looks very promising! I'll report back if I'm still hitting trouble. (The only nagging issue was that after `make install`---hence having both /usr/bin/xfsettingsd and /usr/local/bin/xfsettingsd---for some reason the "Mirror display" option was greyed out. I suspect it's some issue with having both binaries installed at the same time, but I can't say.) -- You received this bug notification because you are a member of Desktop Packages, 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 Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: Incomplete Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in xfce4-settings package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308105]
I tested Alexander's patch, and although I'm not yet sure if it helps with the xfsettingsd crash, the approach is buggy. First I notice that 'Mirror displays' option is now disabled, and each time I switch from one option to the other, 4 instances of the display window are being opened. Overall, not the way to go. @André It would be great if you could post an updated version of Sean's patch! -- You received this bug notification because you are a member of Desktop Packages, 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 Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: Incomplete Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in xfce4-settings package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308105]
@André
I've tried your instructions, but now Sean's patch no longer applies cleanly to
master:
sh>patch -p1 < "sean_fix_for_bug11107.patch" (3834)
patching file xfsettingsd/displays.c
Hunk #2 FAILED at 407.
1 out of 6 hunks FAILED -- saving rejects to file xfsettingsd/displays.c.rej
sh>patch -p1 < "sean_fix_for_bug11107.patch" (3834) returned '1'
>cat "displays.c.rej" (3854)
--- xfsettingsd/displays.c
+++ xfsettingsd/displays.c
@@ -407,7 +407,7 @@
gpointer data)
{
XfceDisplaysHelper *helper = XFCE_DISPLAYS_HELPER (data);
-GPtrArray *old_outputs;
+GPtrArray *new_outputs;
XfceRRCrtc *crtc;
XfceRROutput *output, *o;
XEvent *e = xevent;
>cat "displays.c.rej" (3854) returned '0'
--
You received this bug notification because you are a member of Desktop
Packages, 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
Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
Confirmed
Status in xfce4-settings:
Incomplete
Status in nvidia-graphics-drivers package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-331 package in Ubuntu:
Invalid
Status in xfce4-settings package in Ubuntu:
Confirmed
Bug description:
I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new
behavior that if the TV is power cycled it no longer detects a link
with the HTPC.
When this happens I can find in the xorg log that there is an
accompanying log item:
[ 39829.509] (II) NVIDIA(0): Setting mode "NULL"
After debugging with NVIDIA at
https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being-
detected/ we've deteremined it's a X client that reacts to the RANDR
events causing the mode to be set to NULL.
Working through the list in an Xfce environment, the culprit is
xfsettingsd. If xfsettingsd is running, it causes the TV to come up
in a NULL mode. If it's killed, it remains in the mode it was
previously running in.
Until this is fixed, this behavior can be worked around with a simple shell
script:
==
#!/bin/sh
#Fix TV state when HDMI link is lost.
#By Mario Limonciello
OUTPUT="HDMI-0"
BAD_MODE="1280x720"
GOOD_MODE="1920x1080"
for MODE in $BAD_MODE $GOOD_MODE; do
DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
sleep 2
done
==
To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308105]
Hi! Unfortunately this doesn't seem to help in my case. I've installed a patched 4.11.3 (from my PPA here: https://launchpad.net/~landronimirc/+archive/ubuntu/collection , includes fix_for_bug11107.patch), then logged out, logged in. Then: - connect HDMI cable for external display - in simple dialog select Display #2 (right-most choice) - then select Display #1 (left-most choice) - then unplug HDMI cable More often than not this is sufficient to trigger the xfsettingsd crash. -- You received this bug notification because you are a member of Desktop Packages, 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 Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: Incomplete Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in xfce4-settings package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308105]
I suspect that I'm seeing the same issue as the original poster. Running xfce4-settings 4.11.3, without any of the published patches. When unplugging the HDMI cable I very often get an 'xfsettingsd' crash. This results in Xfce reverting to some fallback, default (and ugly) theme, as well as the font size changes. When it crashes, I get this message in the console: liv@liv-inspiron:~$ The program 'xfsettingsd' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRRCrtc (invalid Crtc parameter)'. (Details: serial 1191 error_code 148 request_code 140 minor_code 21) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) l A quick and dirty, but useful solution is to then run 'xfsettingsd' from a terminal. This reverts from the ugly theme to the usual desktop appearance settings. In any case, I've just upgraded from 4.11.2 to 4.11.3, and this bug has suddenly become all the more visible... -- You received this bug notification because you are a member of Desktop Packages, 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 Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in xfce4-settings package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1114406] Re: Gtk.TreeModelSort does not init properly
Concerning catfish, here it fails to run with the following message: liv@malou-laptop:~$ catfish python: can't open file 'bin/catfish.py': [Errno 2] No such file or directory Would it help if I backported python-gi to work around this issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1114406 Title: Gtk.TreeModelSort does not init properly Status in “pygobject” package in Ubuntu: Confirmed Bug description: In python-gi, attempting to use Gtk.TreeModelSort(child_model), raises TypeError, saying it takes no arguments. This is incorrect. Gtk.TreeModelSort uses a child model as its argument. This works correctly in both quantal and raring, but not precise. The init api is still the same from pyGTK... http://www.pygtk.org/docs/pygtk/class-gtktreemodelsort.html Example code: from gi.repository import Gtk model = Gtk.ListStore(GdkPixbuf.Pixbuf, str, str, str, float, str, bool, bool) sort = Gtk.TreeModelSort(model) Raises: TypeError: GObject.__init__() takes exactly 0 arguments (1 given) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-gi 3.2.2-1~precise ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35 Uname: Linux 3.2.0-37-generic i686 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 Date: Sun Feb 3 10:48:09 2013 InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pygobject UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1114406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
