And a small variation:
trusty 1 b) BUT with light-locker disabled - result: nothing
No locking (well light-locker is disabled, no surprise there) and no
suspending. Might it be, that light-locker somehow triggers the suspend?
** Attachment added:
Also, why should the default value for logind-handle-lid-switch
(false) be changed?
The default settings 'revive' the blank-screen-after-unlock bug (at
least for a resume after a lid close triggered suspend). So IMO the
default settings are not correct in this respect.
Your screen staying
Now, b3nmore, the bottom line of your feedback is that the bug does
not affect utopic with default settings.
No (sorry, I should have mentioned, that #20 is from the same system), with the
default settings in utopic we have:
lid action: result:
switch off display
Output of xfconf-query -c xfce4-power-manager -l -v as requested.
** Attachment added: xfpm_xconf
https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545/+attachment/4297392/+files/xfpm_xconf
--
You received this bug notification because you are a member of Ubuntu
Bugs,
In my case (utopic, xfpm 1.4.1), setting the lid close action to 'switch
off display', works as expected: the system does not suspend. I've
attached a xfpm debug log for that case.
** Attachment added: xfpm_debug_switch_off.log
I should add a few things concerning my comments #22 and #23: All outputs are
from a utopic system. For light-locker to work properly in utopic (see
https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1303736?comments=all)
the xfpm xconf setting
apport information
** Tags added: apport-collected utopic
** Description changed:
I've got a hdd for backups, which most of the time is unmounted and sleeping
(spun down). When going into hibernation it spins up shortly before the
computer powers off. This is somehow annoying because it's
Fresh install and update of xubuntu utopic. In this case all settings in
logind.conf are set to their defaults:
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
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
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
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,
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.
--
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
** Changed in: xfce4-power-manager (Ubuntu)
Status: Expired = Confirmed
** Also affects: elementary-icon-theme (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Tray icon is cropped if icon size 20px
+ xfce power-manager/battery applet: tray icon is cropped if
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
system_app_dir/kde4/ and should be mapped to user_app_dir/kde4/ or
more specific: /usr/share/applications/kde4/ -
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
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
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
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
** 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:
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.
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:
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
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
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
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
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
--
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
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
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
** 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.
** 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
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
** Changed in: sqlite3 (Ubuntu)
Status: Fix Released = In Progress
--
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
I took the liberty to changed the status from 'Fix Released' - 'In
Progress' to keep it in the open bug list. Since the issue remains for
trusty, the majority of ubuntu users is still affected (as one can see
by the still growing numbers of dups of kde bug tracker).
--
You received this bug
** 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/1317449
Title:
Please update to a version 3.8.2
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1317449 ***
https://bugs.launchpad.net/bugs/1317449
** This bug has been marked a duplicate of bug 1317449
Please update to a version 3.8.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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:
-
Out of curiosity I've tested the latest official trusty kernel
(3.13.0-30-generic) and found, that this issue is fixed now.
It seems, that one/some of the backports of 3.14-rc1 or later, which
went into the kernel updates, was the one which solved this bug as seen
upstream. I might add, that I
sqlite3 3.8.5-2ubuntu1 is now in utopic.
Thanks. How about trusty?
--
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 about
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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
** No longer affects: sqlite3 (Ubuntu)
** Also affects: sqlite3 (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
Oops, accidentally deleted the affected package sqlite3 (ubuntu). Sorry
for messing things up. But while we are at it, may be we can take
advantage of the situation and raise the severity level to something
higher than wishlist. The current version breaks virtually the usage of
digikam in trusty
*** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
*** 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 Ubuntu
Bugs, 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
I manually added the corresponding issue for digikam
(https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1315932), but it seems,
that most reports aggregate on the kde bug tracker.
In order to motivate a rise of the importance level and to show that there are
a lot of users affected, I
** 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
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
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
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
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:
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
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
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:
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:
Menu entries sourced form /usr/share/applications/kde4/ can not be
hidden using menulibre. When restarting menulibre, it lists two entries
of the modified one (the original and the overwrite in .local) and the
menu still shows the entry (but only one).
I've tested it with
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
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
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 Ubuntu
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 stdin, line 1, in module
File
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 stdin, line 1, in module
File
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
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,
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 notification
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
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
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
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
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
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.
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:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171411
Title:
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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171411
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171411
Title:
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: 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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171411
Title:
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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171411
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171411
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
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.
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:
101 - 200 of 309 matches
Mail list logo
