This is indeed no longer a problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/601897
Title:
Retention policy "Delete all but the most recent xx messages" deletes
most
This issue is fixed in bionic due to the switch to amarok 2.9.0 (which
contains respective commits).
** Tags added: artful
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to amarok in Ubuntu.
https://bugs.launchpad.net/bugs/1532180
Title:
Corresponding report on the debian bug tracker: https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=851945
** Bug watch added: Debian Bug tracker #851945
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851945
--
You received this bug notification because you are a member of Desktop
Packages,
** Tags added: zesty
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to amarok in Ubuntu.
https://bugs.launchpad.net/bugs/1532180
Title:
Amaroks Wikipedia applet does not work anymore, due to Wikimedias API-
change for https://
Status
** Tags added: yakkety
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to amarok in Ubuntu.
https://bugs.launchpad.net/bugs/1532180
Title:
Amaroks Wikipedia applet does not work anymore, due to Wikimedias API-
change for https://
I've tested the patch against the xenial amarok package
(2:2.8.0-0ubuntu9) and it solves the issue for it too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to amarok in Ubuntu.
https://bugs.launchpad.net/bugs/1532180
Title:
Amaroks
The attached patch fixes the issue for trusty. Since there were only
minimal updates to amarok for xenial, it probably works for it too.
Its basically a backport of the following upstream commits:
http://commits.kde.org/amarok/8c15258b28870b6d9990b24f87ce913e2049bac8
I could not reproduce it either since a while (thats, why I didn't sent
any debug logs). So I concur, that it got fixed by some update.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
New version of firetray (0.6.1) should fix this issue (for now).
** Changed in: firefox (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1575708
Ok, this is somehow extensions related. Starting with --safe-mode
results in a working version.
In my case I pinned it down to the firetray addon. Since it is
unmaintained, I guess this is a won't fix.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Public bug reported:
A freshly updated firefox (to 46) does not work anymore if there is
already a firefox profile. Basically everything is broken: sessions,
menus even browsing by typing in a web address.
As a work around (sort of), one can delete the profile (~/.mozilla) and start
fresh ...
Fedora fixed this in June 2015. If a read their solution correctly (
https://pkgs.fedoraproject.org/cgit/rpms/amarok.git/commit/?id=fa50109140fa4482bbd1ced79ed4daf440f568ee),
it's just a matter of pulling in the upstream commit mentioned in the
op.
** Tags added: trusty
--
You received this bug
Public bug reported:
Amaroks wikipedia applet stopped showing any information. According to
the upstream bug report (https://bugs.kde.org/show_bug.cgi?id=349313)
this is caused by a change in wikipedias api, which requires now a ssl
connection. This means, that all amarok versions currently
Public bug reported:
In an environment where remote cups printers are available, the cups
browsed service does not stop cleanly causing the system shutdown/reboot
to stall until its timeout (90 s) is reached.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups-browsed 1.4.0-1
Public bug reported:
The shadow region of Gtk3 apps drawing their own frame shadow (CSD) is
not transparent for mouse events. E.g. when such an app is in front of a
browser window, a link in the browser can only be clicked/hovered at
distance from the window border, which is larger than the
Another workaround, at least for those not requiring the a11y-indicator
(accessibility menu for visual impaired): removing the a11y-indicator
from the lightdm session, seems to prevent the start of the sound-
indicator. Hence the sound-indicator does not block the termination of
lightdm session,
On a closer look, pressing the brightness up or down key makes a
difference: With the up key brightness is set to its highest level, with
the down key its set to the highest level - 1.
Btw. the newest driver 2:2.99.916+git20141006.ec2b9ac8-0ubuntu0sarvatt
shows the same behavior.
--
You
Public bug reported:
After logout, switching to another login screen or shutting down the
monitor brightness is set to its lowest level, making it rather hard to
read in bright environments. Pressing a brightness key once (up or down
does not matter) sets the monitor brightness to its highest
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
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:
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
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
According to Robert Ancell
(https://answers.launchpad.net/lightdm/+question/250693) the lightdm
upstart user-session should clean up after itself; therefor I'm linking
this issue to upstart.
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
-
This is now fixed upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=80033
** Bug watch added: freedesktop.org Bugzilla #80033
https://bugs.freedesktop.org/show_bug.cgi?id=80033
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1322275
Title:
lightdm sessions started by dm-tool lock
*** This bug is a duplicate of bug 1291075 ***
https://bugs.launchpad.net/bugs/1291075
** This bug has been marked a duplicate of bug 1291075
printer icon does not disappear
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
*** This bug is a duplicate of bug 1294899 ***
https://bugs.launchpad.net/bugs/1294899
** This bug has been marked a duplicate of bug 1294899
Import saved VPN connection has been Recently Broken
--
You received this bug notification because you are a member of Desktop
Packages, which is
When I start scp-dbus-service.py with --debug, I get the attached log. After
finishing the first print job it hangs at:
job-completed-successfully
Connected as user XXX
Authentication pass: 1
Authentication: password callback set
open notifications: 1
num_jobs: 1
num_jobs_when_hidden: 0
Upset
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 Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1293606
Title:
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 Desktop
Packages, which is subscribed to
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:
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
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
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
Public bug reported:
One is probably the original one from gnome: Archive Manager
The other the patched one: Archive Edit View Help
file-roller 3.10.2.1 on xubuntu 14.04.
** Affects: file-roller (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
One is probably
Ok, thats weird: I still get the striped borders occasionally on a fully
updated trusty, but only when I use the Greybird-compact xfwm4 theme (or so it
seems). I replaced therefore all the left-*, right-*, bottom-* xpms of the
theme with those of the normal Greybird theme and didn't see striped
Workaround from #0 still necessary in xubuntu 13.10 and 14.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1022962
Title:
LXDE, apparmor: Show Containing Folder button failed to
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
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
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
apport information
** Tags added: reproducible ubuntu
** 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
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1171411/+attachment/3946134/+files/BootLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
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 Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1171411/+attachment/3946136/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1171411/+attachment/3946137/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
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 Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1171411/+attachment/3946150/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
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 Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1171411/+attachment/3946151/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
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 Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
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 Desktop
Packages, which is subscribed to xserver-xorg-video-intel in
apport information
** Attachment added: xserver.devices.txt
https://bugs.launchpad.net/bugs/1171411/+attachment/3946154/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1171411/+attachment/3946147/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
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 Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
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 Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
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 Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
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 Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
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 Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: LightdmGreeterLogOld.txt
https://bugs.launchpad.net/bugs/1171411/+attachment/3946140/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in
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 Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
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 Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1171411/+attachment/3946138/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in
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 Desktop
Packages, which is
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
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
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 Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
Same in single user mode, so I guess its a kernel issue.
** Package changed: xserver-xorg-video-intel (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
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
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
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.
From the crash file:
ProcCmdline: /usr/bin/X -core :1 -auth /var/run/lightdm/root/:1 -nolisten tcp
vt7 -novtswitch
Starting a xserver with vt7, when there is already a xsession running on
vt7 is a bad idea. Should this be even possible at all? Anyway, I think
we should make sure, that either
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:
Public bug reported:
I'm trying to enable a reliable hibernate/resume cycle on a intel haswell
cpu/gpu system with ubuntu 13.10 +xfce. Until now I've failed, because I get
three possible outcomes, when resuming (without seeing any pattern). In all
cases pm reports, that 'Image restored
It seems lightdm tries to open the new session at vt7 (where the orignal
xsession is already running) instead of a vt8 (or whatever is unused).
It partially succeeds, resulting is this weird state, where parts of
both, original xsession and lightdm, are displayed and input is shared.
**
Public bug reported:
Got this on xubuntu 13.10:
When I logout and login again and start gdmflexiserver (or any other dbus call
to displaymanager), the screen turns black with the mouse cursor still visible.
The session is still running since I can terminate it by executing 'blindly'
the normal
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1248948/+attachment/3902403/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
apport information
** Tags added: apport-collected saucy third-party-packages
** Description changed:
Got this on xubuntu 13.10:
When I logout and login again and start gdmflexiserver (or any other dbus
call to displaymanager), the screen turns black with the mouse cursor still
visible.
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1248948/+attachment/3902406/+files/ProcEnviron.txt
** Changed in: lightdm (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Desktop
Packages,
apport information
** Attachment added: LightdmUsersConfig.txt
https://bugs.launchpad.net/bugs/1248948/+attachment/3902405/+files/LightdmUsersConfig.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1248948/+attachment/3902404/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
Unfortunately Adobe will change the version of their extended support
release from 10.3 - 11.7 (on Windows and Mac). From
http://helpx.adobe.com/flash-player/kb/archived-flash-player-
versions.html :
Beginning July 9th, 2013, we will be updating the version of our
extended support release from
Please provide an installer (or adapt the existing) for flashplayer 10.3
for people with cpus without sse2. According to
https://www.adobe.com/support/programs/policies/supported.html 10.3 is
still supported by adobe (which means it gets security fixes), although
I couldn't find anything about
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:
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 Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/987578
Title:
Evince is not allowed to use
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
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 Desktop
Packages, which
88 matches
Mail list logo
