Jarno, I think it is OK that the older bug was marked as a duplicate
because this newer one has more information and developer activity. The
bug is in xfce4-session, not in xscreensaver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Jarno, the important bug is not in xscreensaver but in whatever calls
xscreensaver-command. However there is also an issue in xscreensaver
that makes the other bug much more prominent. I therefore have kept this
bug report for tracking the xscreensaver part, which is fixed in
xscreensaver 5.22-1.
Thanks for the extra information. Since it is fixed in 13.10 I'll close
this bug report.
** Summary changed:
- laptop-detect gives wrong answer on a laptop (13.10)
+ laptop-detect gives wrong answer on Lenovo T410s
** Changed in: laptop-detect (Ubuntu)
Status: New = Fix Released
--
You
Upstream is favorable to the isatty() hack. I have sent him a patch, and
I will also apply it in Debian's 5.22-1 (to be released real soon). I
have also applied this to the pre-release in my PPA if anyone wants to
test it.
Thaddäus, can you please advice in bug 1054299 on which program is
calling
For the reference it would be good if you at least post the brand and
model.
Also if you could post the cat
/sys/devices/virtual/dmi/id/chassis_type output it could confirm that
the patch in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659404 is
a good idea.
** Bug watch added: Debian Bug
Thanks, but I forgot the sudo, please try:
sudo sh -x /usr/sbin/laptop-detect
Also, please give the output from:
cat /sys/devices/virtual/dmi/id/chassis_type
What kind of a laptop is this (brand, model, etc)? Does it have a
battery?
Eventually, the whole output from sudo dmidecode could be
Thaddäus, that is well spotted and a good idea. The existing sleep(1)
call is kind of a hack. Maybe it can be enhanced with another hack: Skip
the sleep if isatty() returns failure. I will ask upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: xscreensaver (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170987
Title:
xscreensaver activates after logging in
To manage
Thanks for your report. Can you please run:
sh -x /usr/sbin/laptop-detect
and paste the output here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231757
Title:
laptop-detect gives wrong answer
Can anyone (other than qman) confirm that the raring-proposed package
fixes the issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083032
Title:
Video driver not working for Savage chipset
To
I have a pre-release for xscreensaver 5.22 in my PPA, if anyone wants to
install that instead. It is the Debian version without Ubuntu patches,
so you might want to remove the old packages before installing these to
avoid certain upgrade issues. The Precise package should work fine in
any newer
** Bug watch added: freedesktop.org Bugzilla #65444
https://bugs.freedesktop.org/show_bug.cgi?id=65444
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=65444
Importance: Unknown
Status: Unknown
** Changed in: xserver-xorg-video-savage (Ubuntu)
** Package changed: xscreensaver (Ubuntu) = lubuntu-meta (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1202908
Title:
Xscreensaver: failed to execute it on Lubuntu saucy
To manage
** Tags removed: bitesize
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1196251
Title:
pacman crashed with SIGSEGV in is_bonus_dot()
To manage notifications about this bug go to:
Great, I also sent a patch upstream :)
http://anonscm.debian.org/gitweb/?p=collab-
maint/xscreensaver.git;a=commitdiff;h=8df7ba6597ebafe5321c66846f22ee9326902d49
but never heard back from him. So it will be fixed in Debian as soon as
I get to release a 5.21 package.
--
You received this bug
The upstream fix is correct and complete, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1116006
Title:
xscreensaver-settings breaks imageDirectory line if it is a URL
To manage
Possible off-by-one here, there are only NUM_BONUS_DOTS (4) bonus points, so
index 4 is bad:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/xscreensaver/saucy/view/head:/hacks/pacman_level.c#L542
(and on line 556)
The array of bonus_dot bonus_dots[NUM_BONUS_DOTS] is defined on
I am pretty sure it is the same problem and solution in Saucy. Here is a
debdiff for Saucy.
For upstream, I think Cyril's 02- Debian patch is a prerequisite and it
hasn't been upstreamed either, so dualview is simply broken upstream. I
will (re)post that one together with my one on xorg-devel
** Description changed:
- [Impact]
- For xserver-xorg-video-savage: Display corruption in X on (at least) Thinkpad
T22 laptops, making the system unusable.
+ [Impact]
+ For xserver-xorg-video-savage: Display corruption in X on all Savage-equipped
laptops such as Thinkpad T22, making the system
-arch-when-built-with-no-XAA.patch
- 130-Really-fix-up-default-accel-arch-when-built-with-no-.patch
-- Tormod Volden debian.tor...@gmail.com Tue, 07 May 2013 22:47:50 +0200
(not sure why the janitor did not send this out, missing #?)
** Changed in: xserver-xorg-video-savage (Ubuntu
Good luck getting the gnome-screensaver guys to acknowledge that some
people want to use a non-gnome screensaver :)
Please explain again why this is a bug in gnome-screensaver? If you call
org.gnome.ScreenSaver, expect gnome-screensaver to act on it. The
solution would be something like Julien
Please attach files one by one, plain text.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1183420
Title:
Black screen with dual-head on Matrox G45FMDVP32DB /32MB /DVI /VGA
To manage notifications
Thanks! That line 3170 in the patched Ubuntu version is line 3125 upstream:
pMga-RestoreAccelState(pScrn);
Other occurences of this function pointer have been guarded with XAA ifdefs, so
it is only initialized if XAA is available in the server. XAA disappeared after
Precise IIRC so this
Ok, I am glad the crashes went away. I think we should treat the initial
black screen in another bug report, so it doesn't hold up this crash
fix. Can you please then post logs from the initial dual screen run
(black screen), single screen run and successful dual-screen run?
Please also include
What was the latest version (xserver and driver) where this worked?
It might not be too difficult to fix this if you can provide a full
backtrace. Please see https://wiki.ubuntu.com/DebuggingProgramCrash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Could you create a new upstream release for savage so I can pull this
to saucy?
Maarten, I will also try to sort out some other issues before I make a
new upstream release. Distros can make git snapshots at any point. I
would like you to commit these patches to Saucy because I want to have
them
Maarten, by the way, I do intend to package a snapshot for Debian soon,
so you can just sync it to Saucy later (I don't think the single Ubuntu
patch for PCI instead of AGP is needed any longer). But before that, it
would simplify SRU if the above patch has been wetted in Saucy.
--
You received
For those of you who are already on Raring (Ubuntu 13.04), I have
uploaded PPA packages (builds in 6 hours from now). To get this fixed in
the official Ubuntu repositories, it is a longer journey. First it must
be fixed in current development version Saucy.
Attached is a debdiff for Saucy
** Patch added: debdiff for Saucy (xserver-xorg-video-savage)
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-savage/+bug/1083032/+attachment/3674523/+files/xserver-xorg-video-savage_2.3.6-0ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Here are SRU patches for Raring, once we get that far...
** Patch added: SRU debdiff for Raring (xorg-server)
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-savage/+bug/1083032/+attachment/3674524/+files/xorg-server_1.13.3-0ubuntu6.1.debdiff
--
You received this bug
** Patch added: SRU debdiff for Raring (xserver-xorg-video-savage)
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-savage/+bug/1083032/+attachment/3674525/+files/xserver-xorg-video-savage_2.3.6-0ubuntu1.1.debdiff
--
You received this bug notification because you are a member of
Someone with the right super powers please set the linux task to Fix
committed. The patch is in the main tree (for 3.10), and is also queued
up for 3.0, 3.4, 3.5, 3.8 and 3.9 stable branches.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1083032 ***
https://bugs.launchpad.net/bugs/1083032
** This bug has been marked a duplicate of bug 1083032
Video driver not working for Savage chipset
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
For Quantal please try the packages from my PPA
https://launchpad.net/~tormodvolden/+archive/ppa/+packages?field.series_filter=quantal
You'll need both the new xorg-server 2:1.13.0-0ubuntu6.3~bug1083022 and
savage 1:2.3.6-0ubuntu1.1~tormod~q packages. You may add the PPA for
simplicity, there are
Installing new version of config file /etc/laptop-mode/conf.d/hal-polling.conf
...
mt.conf ...
* Enabling laptop mode...
dpkg: error processing laptop-mode-tools (--configure):
subprocess installed post-installation script was killed by signal (Terminated)
Setting up liblist-moreutils-perl
*** This bug is a duplicate of bug 428469 ***
https://bugs.launchpad.net/bugs/428469
** This bug has been marked a duplicate of bug 428469
hdparm and ata_id makes USB drive hang
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Pretty much one year later, I looked at this again and found out that my
USB-IDE bridge does not support the ATACB commands that were sent to it.
This patch is now propagating into the kernel:
https://git.kernel.org/cgit/linux/kernel/git/gregkh/usb.git/commit/?h
** Bug watch added: freedesktop.org Bugzilla #63279
https://bugs.freedesktop.org/show_bug.cgi?id=63279
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=63279
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
It looks more like a bug in the OpenGL driver. Does it only happen with
the closed-source nvidia driver?
** Changed in: xscreensaver (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
22 hours and no response, what a useless testing crowd. I uploaded a
patched xorg-server-lts-quantal to my PPA as well and tested it on my
Precise setup. It now works better when using EXA (kernel module gets
loaded and DRI works). But after a server restart (logout/login) it
locks up again.
I added a possible fix (taken from upstream 1.14) to the xorg-server package in
my PPA:
https://launchpad.net/~tormodvolden/+archive/ppa/+packages?field.series_filter=quantal
Can somebody please test it on 12.10?
The bug is also seen on Gentoo with the 1.13 xserver:
Public bug reported:
There is no way to build any xorg packages once you have installed
xserver-xorg-lts-quantal, because it kicks xserver-xorg-dev out and
there is no xserver-xorg-dev-lts AFAICS.
** Affects: xorg-lts-quantal (Ubuntu)
Importance: Undecided
Status: New
--
You
Sorry I must have been blind, there is xserver-xorg-dev-lts-quantal
** Changed in: xorg-lts-quantal (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132964
Title:
I have to blame bash autocompletion of apt- commands which stopped
working (after upgrading xorg stack?).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132964
Title:
missing lts -dev package
To
baltasarq, I meant EXA without DisableTile. We know already that the
latter works.
Anyway, I got the chance to look at this and was able to reproduce using
the lts-quantal stack. Trying EXA just after XAA had messed up caused a
total lock-up, but after reboot EXA seems to work, although things
I talked too soon. EXA wasn't really running because the savage kernel
module had not been loaded (new kernel after I rebooted, since the xorg-
lts upgrades the kernel as well) for some reason. After loading the
kernel module and restarting (with EXA) I got a full lock-up again.
--
You received
BTW, did anyone try Option AccelMethod EXA?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083032
Title:
Video driver not working for Savage chipset
To manage notifications about this bug go to:
Michael, thanks for the testing. This is very helpful. Can you please
also attach your Xorg.0.log?
I can not promise to get to this the next few weeks, but the first thing
I will do is to build a debug build of the savage driver (add -DTRACEON
to CFLAGS in debian/rules) both before and after
*** This bug is a duplicate of bug 1083032 ***
https://bugs.launchpad.net/bugs/1083032
If you choose the vesa driver you may have reduced functionality. There
was another workaround in the link in bug 1083032:
Section Device
Identifier mydearsavage
Option DisableTile
EndSection
If
Oh sorry, I thought Ubuntu was using the same Debian patches. Well there
must be another reason for this issue in Ubuntu then. I'll move the
status back to Confirmed, it was not me who confirmed it.
Is it acpi-support that calls xscreensaver-command on a standard
installation of Xubuntu 12.10? I
I can confirm this on xscreensaver 5.21 on Debian unstable with xfce as
well. The problem is that the xscreensaver daemon is told to lock the
screen only after the computer has woken up. Using xscreensaver -debug I
can see that it receives the THROTTLE ClientMessage before the sleep,
but the LOCK
** Bug watch added: Debian Bug tracker #700696
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700696
** Also affects: acpi-support (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700696
Importance: Unknown
Status: Unknown
--
You received this bug notification
Thanks for testing. I can confirm this (at least a slash is taken away)
on Ubuntu 12.04.
If Ubuntu 13.04 does not get xscreensaver 5.20 (or newer) a separate bug
fix for 5.15 would be possible.
** Changed in: xscreensaver (Ubuntu)
Status: New = Confirmed
--
You received this bug
Well, usually only serious bugs get fixed in a released Ubuntu version.
This seems a bit unfortunate, but most developer efforts are spent on
fixing bugs in the _next_ release (and adding features...).
If someone files an SRU request, it will be considered for e.g. 12.10.
See comment 16, anyone
I thought Ubuntu had got rid of acpi-support. Is this an upgraded
installation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067140
Title:
Closing laptop lid locks even with lock: False
To
I belive this is due to pam_ecryptfs and nothing in the screensaver
packages.
** Package changed: xscreensaver (Ubuntu) = ecryptfs-utils (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085706
Interesting bug, but I don't see it with 5.20 on Debian.
I already contacted the author of xscreensaver directly, but he
refuses to even read bug reports for a two year old version
(understandable...)
Yawn, just play along. 5.15 was his newest release only 7 months ago...
The newer releases are
*** This bug is a duplicate of bug 1083032 ***
https://bugs.launchpad.net/bugs/1083032
** This bug has been marked a duplicate of bug 1083032
Video driver not working for Savage chipset
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: xserver-xorg-video-savage (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954569
Title:
paquete de configuracion de video
To manage
I believe this bug was fixed in savage driver 2.3.3 (Ubuntu 12.04).
** Changed in: xserver-xorg-video-savage (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It was already fixed in 13.04 as of comment 17 (raring=13.04).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1077186
Title:
ignores EXIF rotation data from Nikon cameras
To manage notifications
Yes, try that. Unless something else holds it back (package
dependencies), you should be fine without. I don't have acpi-support on
my 12.04 Lubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am not able to reproduce this on my Savage TwisterK, so I wonder if it is
limited to certain cards. Can everybody affected please post the output from:
lspci -d 5333: -nn
I am not running 12.10 on my poor laptop though, but it has 12.04 and kernel
3.7.4 and xf86-video-savage from latest
What exactly is not working? Video playback (XV) or simply not being
able to anything on the screen? Is it the same symptoms as in bug
#1083032?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110905
*** This bug is a duplicate of bug 1083032 ***
https://bugs.launchpad.net/bugs/1083032
No, you're not the only user :) Your log shows that the savagefb driver
is being loaded. Unless you want to use this framebuffer driver (not X)
this should not happen. Try blacklisting it.
--
You received
I see. Just attach /var/log/Xorg.0.log and dmesg output for a start. You
can use the vesa driver by specifying it in xorg.conf but then apport-
collect would attach the vesa log instead of the savage log anyway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Yes, that is supposed to attach a number of logs and information. The
same that would have been attached if you had filed the bug using
ubuntu-bug xserver-xorg-video-savage.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I meant apport-collect 1098661 without the hash sign.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098661
Title:
acer aspire 1300 (S3 ProSavage) dsiplays distorted image after
upgrading from
A Savage user! I knew there was one :) Can you please run apport-
collect #1098661 so I get all logs and details?
** Changed in: xserver-xorg-video-savage (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I believe you can disable the fading out in xscreensaver, please see its
settings (run xscreensaver-demo) or the man page and try it out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1015297
Title:
This seems to be fine in Ubuntu 12.04.
** Changed in: sysvinit (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/214795
Title:
fsck recovery shell has
Actually the problem was that /usr/lib/thunderbird/extensions was a real
directory on this system instead of a soft link to ../thunderbird-
addons/extensions .
Removing the thunderbird package and reinstalling it fixed the issue.
So something goes wrong in the upgrade path.
** Summary changed:
** Description changed:
$ dpkg -l thunderbird* | grep ^ii
ii thunderbird17.0+build2-0ubuntu0.10.04.1
Email, RSS and newsgroup client with integrated
spam filter
ii thunderbird-locale-nb
Public bug reported:
This is up-to-date Ubuntu 10.04.4 LTS.
$ ubuntu-bug thunderbird-locale-nb
hook /usr/share/apport/package-hooks//source_thunderbird.py crashed:
Traceback (most recent call last):
File /usr/lib/python2.6/dist-packages/apport/report.py, line 636, in
add_hooks_info
Public bug reported:
$ dpkg -l thunderbird* | grep ^ii
ii thunderbird17.0+build2-0ubuntu0.10.04.1
Email, RSS and newsgroup client with integrated spam
filter
ii thunderbird-locale-nb
The Error Console shows:
Could not read chrome manifest
'file:///home/user/.thunderbird/abcdefgh.default/extensions
/nb...@dictionaries.addons.mozilla.org/chrome.manifest'.
but I don't know if the dictionary should be included in the language
pack or if this folder is just a leftover from an
I have looked at https://developer.mozilla.org/en-
US/docs/Installing_extensions and I believe the xpi file is in the wrong
location. After running:
sudo ln -s /usr/lib/thunderbird-addons/extensions
/usr/lib/mozilla/extensions/\{3550f703-e582-4d05-9a08-453d09bdfdc6\}
(where
I can not get this to work on Ubuntu 12.04. I have gnome-user-share
installed (don't remember if it was by default) and used Personal File
Sharing to enable Receive Files in Downloads folder over Bluetooth
(tried enable Share public files over Bluetooth as well). The Nokia
5800 just complains
In my desperation I tried a 0a12:0001 Cambridge Silicon Radio, Ltd
Bluetooth Dongle instead of the built-in (0a5c:200a Broadcom Corp.
BCM2035 Bluetooth dongle), and I got the file transferred. However I got
a kernel Oops and dbus and compiz crashing before a total lock-up. Oh
well, I guess we
gdk-pixbuf_2.26.4-0ubuntu1
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1077186/+attachment/3436716/+files/gdk-pixbuf_2.26.4-0ubuntu2.debdiff
** Changed in: gdk-pixbuf (Ubuntu)
Status: In Progress = Confirmed
** Changed in: gdk-pixbuf (Ubuntu)
Assignee: Tormod Volden
BTW, the debdiff touches the Uploader line in debian/control because the
Ubuntu delta is broken - that file is generated from control.in so this
change happens when I run debuild.
This should obviously be fixed in Raring as well, but I am not preparing
a debdiff because I expect upstream to apply
I have found the error in the above mentioned upstream commit, and I
will send a patch upstream for review.
** Changed in: gdk-pixbuf (Ubuntu)
Status: Confirmed = In Progress
** Changed in: gdk-pixbuf (Ubuntu)
Assignee: (unassigned) = Tormod Volden (tormodvolden)
** Summary changed
** Bug watch added: GNOME Bug Tracker #688427
https://bugzilla.gnome.org/show_bug.cgi?id=688427
** Also affects: gdk-pixbuf via
https://bugzilla.gnome.org/show_bug.cgi?id=688427
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
I was able to reproduce this on a Ubuntu 12.10 Live CD (amd64). It can
be seen in the ltrace below that gdk_pixbuf_apply_embedded_orientation()
is called but returns the same pixbuf (no transformation done). In
Ubuntu 12.04 the same function returns a new pixbuf and we can see the
width and length
This was a regression in this release:
gdk-pixbuf (2.26.4-0ubuntu1) quantal; urgency=low
* New upstream bugfix release
-- Robert Ancell email address hidden Tue, 18 Sep 2012 17:06:38 +1200
I am pretty sure the upstream commit http://git.gnome.org/browse/gdk-
pixbuf/commit/gdk-pixbuf/io-
Thanks for your report. Your second, correct photo does not have any
EXIF data, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1077186
Title:
glslideshow ignores EXIF rotation data from Nikon
I don't think this is an xscreensaver bug, on Ubuntu it uses libgdk-
pixbuf to read the jpeg files. I have to look closer another day, but
for now I tested firefox (wrong) and eog (right) on Ubuntu 12.04. After
resetting the orientation tag to top- left using the tool from
FWIW, if you run xscreensaver-getimage -verbose -file image-file.jpg
it should print a message if libgdk-pixbuf is rotating the picture.
Otherwise gdk_pixbuf_apply_embedded_orientation() could be at fault.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Redmar, did you send the patches to jwz?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/665820
Title:
Translated screen saver descriptions not used
To manage notifications about this bug go to:
** This bug is no longer a duplicate of private bug 1056858
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063802
Title:
maze crashed with SIGSEGV in __libc_start_main()
To manage notifications
*** This bug is a duplicate of bug 924278 ***
https://bugs.launchpad.net/bugs/924278
** This bug has been marked a duplicate of bug 924278
xscreensaver doesn't enable DPMS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It should turn off the backlight eventually, but some time after the
screen has been blanked. Does this happen?
If this does not happen, please run this to see if the graphic driver is
capable enough:
xset dpms force off; sleep 7; xset dpms force on
This should turn off the screen (power
It looks like mga_dga.c (line 32) references MGAStormSync even if XAA is
disabled. But Makefile.am does not add mga_storm.c to mga_drv_la_SOURCES
in this case.
** Changed in: xserver-xorg-video-mga (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 956071 ***
https://bugs.launchpad.net/bugs/956071
** This bug has been marked a duplicate of bug 956071
Xorg crashed with SIGSEGV in XIGetDeviceProperty()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Please attach the stacktrace here.
** Summary changed:
- Xorg crash
+ Xorg crash in BasicComputeAcceleration
** Package changed: xorg (Ubuntu) = xserver-xorg-input-synaptics
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
didi_X8, I am not sure your crash is the same issue, it seems yours
bombed out in BasicComputeAcceleration() while in this report it is
XIGetDeviceProperty().
The original poster had XIChangeDeviceProperty+40, whereas I got
XIChangeDeviceProperty+440 which is also seen in http://bugs.debian.org
This might be a duplicate of bug 956071.
** Also affects: xorg-server (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681796
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Mamoru, thanks a lot for investigating this! We'll add
-D_FILE_OFFSET_BITS=64 in the next Debian version.
** Changed in: xscreensaver (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: xscreensaver (Ubuntu)
Assignee: Tormod Volden (tormodvolden) = (unassigned)
--
You received
Thanks for your report and suggested fix!
This has been fixed in my Debian tree and will be released in Debian in
5.15-4 or 5.19-1. Debian is in release freeze at the moment, but I have
uploaded a preview package 5.19-1pre to my PPA if anyone would like to
test it:
This has now been fixed in my Debian tree and will be released in Debian
in 5.15-4 or 5.19-1. Debian is in release freeze at the moment, but I
have uploaded a preview package 5.19-1pre to my PPA if anyone would
like to test it: https://launchpad.net/~tormodvolden/+archive/ppa
--
You received
101 - 200 of 7278 matches
Mail list logo
