apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1171411/+attachment/3946145/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171411
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1171411/+attachment/3946141/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171411
Ti
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1171411/+attachment/3946135/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171411
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1171411/+attachment/3946146/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/117
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1171411/+attachment/3946149/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171411
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1171411/+attachment/3946144/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171411
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1171411/+attachment/3946152/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171411
Title:
xf
apport information
** Attachment added: "LightdmGreeterLog.txt"
https://bugs.launchpad.net/bugs/1171411/+attachment/3946139/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1171411/+attachment/3946142/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171411
Title:
xfwm
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1171411/+attachment/3946153/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171411
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1171411/+attachment/3946143/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171411
Title:
xfwm
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1171411/+attachment/3946148/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171411
Title:
xf
I should mention, that in contrast to the original report, the stippled window
borders appear now independent of the compositor state (on or off).
I've also tested xfwm4 in combination with compton (standalone opengl
compositor) with the same result: occasional appearance of stippled borders.
--
I've updated the packages from the mentioned ppa. Additional to the
border issue I get now quit frequently character distortions (cf. the
second "(II)"- line in the screenshot of the terminal window) in
different programs.
Please note (cf. comment #31), that using a compositor or not does not
seem
Another annotation: I have the striped borders issue also on my desktop
system: xubuntu 13.10, Intel i5-4570S with integrated hd4600 gpu. So I
guess this issue isn't limited to a single set of hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
The patched version works fine for me. However I don't get any 'restart
required'-notification on saucy. Can someone confirm this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246364
Title:
update
This is most likely a dub of https://bugs.launchpad.net/ubuntu/+source
/system-config-printer/+bug/1291075
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1293606
Title:
print icon frozen
To manage n
In my experience this issue occurs mainly with non-local printers.
Somehow the icon does not get removed from systray; a reload/restart of
the panel (e.g. xfce4-panel -r) will remove it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Running system-config-printer-applet --debug from a terminal outputs the
following after starting a print job:
checking for jobs
Starting job applet
ERROR:dbus.proxies:Introspect error on
:1.91:/org/fedoraproject/Config/Printing: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply:
It seems, that scp-dbus-service is somehow effected by printing or the query of
the print-applet: After login (or restart of scp-dbus-service) it can be
queried by e.g.
$ qdbus --session org.fedoraproject.Config.Printing
/
/org
/org/fedoraproject
/org/fedoraproject/Config
/org/fedoraproject/Conf
Another observation: the systray icon gets removed if one kills scp-
dbus-service. However to gain normal functionality (i.e. notification
upon printing) system-config-printer-applet (applet.py) has to be
restarted as well.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
According to https://bugs.kde.org/show_bug.cgi?id=329697 sqlite3 version 3.8.2
causes crashes in digikam (and possibly other software) in various situations.
There are several reports, that versions > 3.8.2 fix the issue.
I'm using the 3.8.4.3 package from debian testing rig
** Summary changed:
- digikam crashed with SIGSEGV in sqlite3_step()
+ digikam 3.5 crashes on several occasions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315932
Title:
digikam 3.5 crashes on s
Since upgrading sqlite3 most likely fixes the issue, I ask for it on:
https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1317449
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to digikam in Ubuntu.
https://bugs.launchpad.net/bugs/1315932
T
Public bug reported:
Using the simple example from upstreams readme
(https://github.com/bear/parsedatetime) raises an error:
$python
>>> import parsedatetime.parsedatetime as pdt
>>> cal = pdt.Calendar()
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-pac
Public bug reported:
Trying to import a vpnc configuration, but the connection editor segfaults when
the configuration file gets loaded:
nm-connection-e[18008]: segfault at 1bd02b0 ip 01bd02b0 sp
7fff768f9e58 error 15
Adding the vpnc profile manually works fine, but in previous vers
Public bug reported:
Digikam 3.5 in trusty may crash in several situations. According to the
following upstream report:
https://bugs.kde.org/show_bug.cgi?id=329697
this is probably related to the sqlite3 version 3.8.2.
** Affects: digikam (Ubuntu)
Importance: Undecided
Status: New
I believe I found a reliable way to reproduce the crash:
- open thunar
- use the side panel to mount a usb stick (or use automount)
- open a document on the usb volume (e.g. a pdf file)
- keep it open and try to unmount the usb stick via the side pane
- cancel the window which informs that the vol
Public bug reported:
When trying to access server settings via gnome gui in trusty I get a
cups server error: "There was an HTTP error: Not found."
Adding/removing printers with the gui works fine. The server settings
are accessible via a web browser and the web interface.
system-config-printer
** Also affects: digikam (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1317449
Title:
Please update to a version > 3.8.2
To manage notifications
** Summary changed:
- Please update to a version > 3.8.2
+ sqlite version 3.8.2 breaks digikam
** Changed in: digikam (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Description changed:
- According to https://bugs.kde.org/show_bug.cgi?id=329697 sqlite3 version
3.8.2 causes crashes in digikam (and possibly other software) in various
situations. There are several reports, that versions > 3.8.2 fix the issue.
+ Please update sqlite to a version > 3.8.2.
+
Public bug reported:
After powering off an usb3 disk (e.g. udisksctl power-off -b /dev/sdc)
the system immediately resumes after suspend. This does not happen, if I
umount the device and disconnect it. Usb devices < 3.0 seem not to be
affected.
How to reproduce:
1) plug an usb3 device to an usb3
> can you please do "dmesg > /tmp/dmesg.txt" after such a resume and
attach /tmp/dmesg.txt here? Thanks!
Rebooted and executed the steps mentioned above. dmesg is attached.
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349879/+attachment/4166687/+files
I did some further testing with following results: I can reestablish the
correct suspend behavior by plugging in the drive, mounting, unmounting
and unplugging the drive without powering down. This has to be done on
exactly the same port, which triggered the misbehavior (other ports will
not work).
I've tested kernel 3.16-rc7 from mainline, with the same results.
Another thing I've tested, is disabling acpi wakeups for usb related
devices: If I disable wakeup for ALL usb related devices (in my case
EHC1, EHC2, XHC) suspend works correctly. Any other combination (e.g.
disable only XHC and lea
> Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.16 kernel[0].
Done. No changes.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
--
Attached a gdb backtrace from running:
G_SLICE=debug-blocks gdb --args Thunar --daemon
To reproduce quite reliably, I have to open a thunar window,
mount/umount e.g. usb drives or network shares, browse some local
folders and close thunar (some times looping through the whole procedure
several tim
backtrace like in the previous comment, but for all threads.
** Attachment added: "all_threads_bt_full.txt"
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/+attachment/4083661/+files/all_threads_bt_full.txt
--
You received this bug notification because you are a member of Ubunt
Public bug reported:
The monitor switch off time (dpms) has no effect (or gets overwritten),
if xfce power manager is setup to control monitor power management. So
light-locker-settings should probably have some way to handle this.
Following comes to my mind: use xfconf to either disable dpms in
Adapted light-locker-settings.py which uses the new module if xfpm is
running.
** Attachment added: "light-locker-settings.py"
https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/1290737/+attachment/4021886/+files/light-locker-settings.py
--
You received this bug notificatio
I've attached a module, which can be used to set/get dpms timings via
xfce4-power-manager. It uses /sys/class/power_supply/AC/online to
determine the power state if existent or assumes on-ac otherwise.
** Attachment added: "xfpmsync.py"
https://bugs.launchpad.net/ubuntu/+source/light-locker-se
If xfce4-power-manager has never been used to change dpms settings, the
default timings are not registered in xfconf. This version makes sure,
that the xfconf properties we use, are created if necessary.
** Attachment added: "xfpmsync.py"
https://bugs.launchpad.net/ubuntu/+source/light-locker-
Same as in #3, but using a more pythonic way.
** Attachment added: "light-locker-settings.py"
https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/1290737/+attachment/4030411/+files/light-locker-settings.py
--
You received this bug notification because you are a member of Ubu
Same as in #4, but using a more pythonic way.
2 remarks:
1) One could easily sync the 'Lock screen when going for suspend/hibernate'
setting of xfpm with the enable/disable light-locker setting (or even the lock
screen setting in the session settings). However this would be a one way sync,
sin
I've played around a bit with the trusty daily image. So far I couldn't
trigger any heavy distortions. The stippled window borders (c.f.
attached screenshot) however still do occur occasionally (but with
reduced frequency than before).
** Attachment added: "xfwm4-stippled_borders.jpg"
https://
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1171411/+attachment/3943332/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171411
apport information
** Tags added: apport-collected trusty
** Description changed:
Since sna acceleration of the intel display driver is enabled by default, I
see two types of display distortions from time to time:
i) windows have some times stippled borders,
ii) xfce4-terminal shows disto
> This should have been fixed by the upgrade to 2.99.909, now 2.99.910.
Unfortunately not for me (c.f. attached screenshot). I still can
reproduce the border issue (with and without the compositor) quite
frequently.
** Attachment added: "trusty_xfwm4_intel_striped_border.jpg"
https://bugs.lau
> > This should have been fixed by the upgrade to 2.99.909, now 2.99.910.
>
> Unfortunately not for me [...]
Oh, wait. Did this mean by upgrading *from* 2.99.909 to 2.99.910? If
so, please ignore my previous comment, since I'm clearly running
2.99.909.
--
You received this bug notification bec
Even 2.99.910 did not fix the issue.
** Attachment added: "trusty_xfwm4_intel_2.99.910_striped_border.jpg"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1171411/+attachment/3975984/+files/trusty_xfwm4_intel_2.99.910_striped_border.jpg
--
You received this bug notifi
Upstream bug report: https://bugzilla.kernel.org/show_bug.cgi?id=66741
** Bug watch added: Linux Kernel Bug Tracker #66741
http://bugzilla.kernel.org/show_bug.cgi?id=66741
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
First login after a fresh (re)start of lightdm, gdmflexiserver results in
following X calls:
2330 /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7
-novtswitch
2587 /usr/bin/X -core :1 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8
-novtswitch
After logout and login I get:
pm-utils 1.4.1-9fix.ubuntu12.04 works for me on precise. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172692
Title:
Please implement in-kernel suspend to both
To manage notifications abou
I can now reproduce it by hibernating two times. As the attached dmesg shows,
resume after first std works fine, resume from the second std onwards results
in no video output.
As it may be a kernel issue, I tested it with the 3.11 saucy and the 3.12 tusty
kernel. Both show the same behavior.
**
I see this in 12.04.3 as well, at least occasionally.
The attached screenshot shows a delayed shutdown/reboot. I've modified
/etc/init.d/sendsigs to ps the ommited pids before killall5 -15 or
killall -9 respectively. Additionally if killall5 -9 is called, all pids
except the kernel threads are pri
Screenshot of a not delayed shutdown/reboot. In this case killall5 -9 is
never called.
** Attachment added: "normal_shutdown.jpg"
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1212142/+attachment/3912793/+files/normal_shutdown.jpg
--
You received this bug notification because you a
Just to summarize the kernel log on failures (and making this issue
easier to locate):
[ 730.725409] [drm:intel_ddi_pll_mode_set] *ERROR* No WRPLLs available!
[ 730.725413] [ cut here ]
[ 730.725429] WARNING: CPU: 1 PID: 2213 at
/build/buildd/linux-3.11.0/drivers/gpu/dr
Attached full dmesg with drm.debug=0xe boot option.
Additionally I unplugged/plugged the dvi/vga port after the second
resume. The log shows, that those events get registered, but still no
video output (monitor goes into power save).
** Attachment added: "dmesg_drm.debug_hotplug"
https://bugs
Precise with kernel 3.2 succeeds to connect the drive on usb 3.0.
** Attachment added: "dmesg_3.2_usb3_success"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1254261/+attachment/3915433/+files/dmesg_3.2_usb3_success
--
You received this bug notification because you are a member of Ubu
Public bug reported:
On a fresh saucey installation (kernel 3.11), I can not use my external
usb 3.0 hdd on usb 3.0 ports, it only works on usb 2 ports. kernel log
shows, that it disconnects immediately after it is plugged in. Then it
continues to connect and disconnect indefinitely (q.v. attached
kernel log of a precise live system with kernel 3.8 failing to connect
the drive on a usb 3.0 port.
** Attachment added: "dmesg_3.8_usb3_failed"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1254261/+attachment/3915440/+files/dmesg_3.8_usb3_failed
--
You received this bug notification
lsusb -v output on 3.2 on usb 3.0 port.
** Attachment added: "lsusb_3.2_usb3"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1254261/+attachment/3915434/+files/lsusb_3.2_usb3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Same drive on saucy when using the usb 2 port.
** Attachment added: "dmesg_3.11_usb2_success"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1254261/+attachment/3915432/+files/dmesg_3.11_usb2_success
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1254261/+attachment/3915467/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254261
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1254261/+attachment/3915465/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254261
Titl
Workaround from #0 still necessary in xubuntu 13.10 and 14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022962
Title:
LXDE, apparmor: "Show Containing Folder" button failed to execute err
To
Public bug reported:
xfpm can change the monitor pm timings depending on the power source
(and settings). It does so by setting the xservers dpms timings for
standby and off accordingly. light-locker-settings configures the
xservers blanking and standby time. This means, if light-locker is
configu
> DPMS sleep/standby/off time is not the same as blank time and xfpm1.2
didn't handle blanking at all.
Thats my point exactly: If xfpm is running light-locker-settings should
not apply any screen blank settings, because xfpm does not handle it.
I've attached a patch which makes light-locker-setti
> You could argue that the DPMS settings conflict and that this one
should be removed though.
dpms don't conflict, because they are synced between xfpm and light-
locker-settings.
> Since no service handles the blank times with the switch away from
XScreensaver to light-locker, we decided that li
Just to be sure there is no misunderstanding, I was talking about light-
locker-settings 1.2.1 and xfpm 1.2.0 (both from trusty). The patch is
for those versions. If you decide to apply it, we will loose a gui to
set screen blanking (it will be turned off), but we will gain better
consistency with
Are you sure? If I use lock session when screensaver is activated, delay: 10s
and xset s 100 dpms 10 0 120. Session locks after 20s.
Same with xset s 0 dpms 10 0 120.
So the first pm event seems to start the timer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
> But the blank timeout is set to 10mins by default ...
Unless there is something hard coded into light-locker, this shouldn't
be an issue: ll-settings will set two timings only and will disable (=0)
the other ones. With xfpm running: xset s 0 dpms t1 0 t2, and without:
xset s t1 dpms t2 0 0.
--
There is a red hat bug report containing a patch, which seems to solve this
issue for me on trusty:
https://bugzilla.redhat.com/show_bug.cgi?id=1116756
And here's the request for applying the path on the debian side:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756878
** Bug watch added: R
I've attached a patched version for trusty, for those who want to make a
quick test. Just replace the original file in /usr/share/system-config-
printer/scp-dbus-service.py with attached one (and make sure it has the
right permissions).
** Attachment added: "scp-dbus-service.py"
https://bugs.l
> A big help would be a test case not involving digikam at all.
Not sure, how to provide such, since the exact cause is unknown.
However, here's a proposal: I've found only one closed ticket for the
3.8.2 branch [1]. Maybe it would be worth backporting the fix [2] and
test, if it fixes the digika
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315558
Title:
Ristretto cannot read GIF properly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
Debian has it too: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=760464
** Bug watch added: Debian Bug tracker #760464
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760464
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
It's still valid for trusty and utopic (with the new xfpm panel plugin),
if the panel size is < 22px. But it's probably more an issue with the
icon theme (elementary), than xfpm. I've reported it upstream:
https://github.com/shimmerproject/elementary-xfce/issues/69
--
You received this bug notifi
Sorry can't test it on precise anymore, since all machines are upgraded
to trusty. But it is fixed in trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978071
Title:
Wrap workspaces when pointer
Same in trusty. Upstream report:
https://bugzilla.xfce.org/show_bug.cgi?id=9983
However, in the xfce bugzilla are reports concerning other issues, which
mention gif images, but don't mention this particular issue. This may
mean, that it is a ubuntu specific bug.
** Bug watch added: Xfce Bugzilla
I've attached a python script which one can use for user switching. It
switches to the login/unlock screen or, if the user disabled light-
locker, directly to its session.
Download it and make it executable; then you can call it from whisker
menu, a launcher or a keyboard shortcut.
** Attachment
Tested again with v3.17.1-utopic: still the same issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349879
Title:
powering off an usb3 device causes kernel to resume immediately after
suspend
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322275
Title:
lightdm sessions started by dm-tool lock never get closed
Same in utopic with xfce4-power-manager 1.4.1-0ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307545
Title:
Power Manager settings are ignored when closing laptop lid
To manage notificatio
To fix this, menulibre should reproduce subdirectories (if existent) to
allow merging of desktop files.
For this case all kde .desktop files are stored in
/kde4/ and should be mapped to /kde4/ or
more specific: /usr/share/applications/kde4/ ->
~/.local/share/applications/kde4/
--
You received t
I can confirm, that evince 3.4.0-0ubuntu1.5 from precise-proposed fixes
the issue for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/987578
Title:
Evince is not allowed to use exo-open
To manage
There are 3 slightly different situations we should clarify when discussing
this bug:
1) the pdf was opened before -> evince open its exactly as it was closed
(should work with newer versions)
2) the pdf wasn't opened before, but default settings were set by the user via
Edit-Menu -> evince uses
Public bug reported:
It will fix most of the recent bugs including #1049937, #664627 and
possibly #779671, #778212.
** Affects: xfce4-places-plugin (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Public bug reported:
Version 0.8.1 causes high cpu times due to a buggy weather data update
procedure (q.v. https://bugzilla.xfce.org/show_bug.cgi?id=9382). As a
bonus it would fix #1066400 as well.
** Affects: xfce4-weather-plugin (Ubuntu)
Importance: Undecided
Status: New
--
You
This is related to a buggy weather data update procedure in version
0.8.1 (q.v. https://bugzilla.xfce.org/show_bug.cgi?id=9382 ). An update
to 0.8.2 would fix this.
** Bug watch added: Xfce Bugzilla #9382
http://bugzilla.xfce.org/show_bug.cgi?id=9382
--
You received this bug notification beca
Public bug reported:
Updating the system with help of the update notifier does not follow a
consistent work flow. For a normal user it should work as follows:
- a notification appears,
- he clicks on the symbol and chooses 'install all updates',
- the updates process starts (possibly asking fo
The issue with files stored in /tmp is fixed upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=680145
** Bug watch added: GNOME Bug Tracker #680145
https://bugzilla.gnome.org/show_bug.cgi?id=680145
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I think this is fixed (or at least improved) in gutenprint 5.2.9. I just
downloaded and installed the quantal packages: printer-driver-gutenprint
and libgutenprint2, and printing improved a lot (colors, speed,
greyscale...). So we may consider backporting it to precise.
--
You received this bug n
Public bug reported:
I've noticed recently for several fresh Xubuntu 12.04 installations
(alternate and desktop), that on all partitions formated by the
installer the filesystem check at boot time is disabled. E.g.
sudo tune2fs -l /dev/sda6 | grep -iE " mount count|check "
Maximum mount count: -1
Did you install the "texlive-fonts-recommended"-package. If not install
it and try again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010909
Title:
permission denied: /usr/bin/{mktexpk,mktextfm}
** Summary changed:
- With Kernel 3.8.0-12 Intel GPU/screen size not recognized, works correctly
with old 3.8.0-12
+ With Kernel 3.8.0-13 Intel GPU/screen size not recognized, works correctly
with old 3.8.0-12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
It may also lead to series display distortion (view attachment), which
renders the UI unusable. Picture taken from a freshly installed Xubuntu
13.04beta1 after the first software update.
** Attachment added: "distortion.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1156548/+attachm
I get glitches too on a freshly installed Xubuntu 13.04beta1 (view attachment).
However in my case it's somehow correlated with the compositor (xfwm4), which
must be switched on to get the artifacts. I don't have gpu hangups.
kernel : 3.8.0-13.23
intel driver: 2.21.4
** Attachment added: "dis2.j
Public bug reported:
With the current build the map features (picking a location on a map or
displaying dive locations on a map) are not available. Building with
libosmgpsmap-dev should provide them.
** Affects: subsurface (Ubuntu)
Importance: Undecided
Status: New
--
You received
201 - 300 of 308 matches
Mail list logo
