## Thanks @vdrok
> automatically lock the session - when the screensaver is activated
> delay locking after screensaver for - 5 seconds
> lock screen when system is going to sleep - checked
Hmm, on my system the delay was set to something small (perhaps even 0).
## Thanks @mag3sh
> From further
I have a question for people experiencing this bug (yes, you included
:-).
Please:
* open xfce4-settings-manager,
* click icon "power manager",
* click tab "security",
* report what settings are there for when to "automatically lock the session",
"delay locking after screensaver for...", "lock
Interestingly, thus bug started to reappear in its extreme form: a few
times in the past days, all letters disappeared in my xfce4-terminals.
Workaround was to close and reopen session.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
To add to my latest comment where I report that problem reappeared a few
times in recent days: same hardware, same usage pattern, on the very re-
installation of 16.04 that had the problem disappear (cf. #comment:77).
Software updates applied regularly since the last near-2-years. Nothing
salient w
Public bug reported:
# Context
* Computer with several X sessions opened.
* Users switching from one opened session to another.
* Lightdm opens new greeter, wait for typing password.
* User types password.
* Password is accepted.
* System closes the current greeter (screen gets black for an insta
As seen in attached files, this is Xubuntu 18.04, where lightdm is
default, no significant local customization.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1776475
Title:
Bug still regularly observed.
This is not the same bug as #1656399 though it share some
characteristics.
In particular, the fact that both bugs do not always occur (but somehow
randomly) suggests that both are linked to a race condition somewhere in
lightdm logic.
--
You received this bug notif
Public bug reported:
# Context
* Xubuntu 18.04 using lightdm, no specific customization, no
xscreensaver/gnome-screensaver.
* Problem observed two machines:
** one machine with several users often swapping sessions,
** one machine with just one regular user who just locks/unlocks session often
Also, the problem is not specific to any user.
It randomly affects any of the users of the machine. At that moment
only that user is affected.
Next time it may affect the same user or another.
We believe that it may affect several users at a time, if we keep the
machine running until problem af
## Log: soon
Thanks @smcv for your feedback.
I believe ubuntu-bug used to automatically attach a number of log files
automatically, it appears it did not this time.
Bug happens several times a week. I have captured a log.
## Workaround!
I wanted to test if running another X session would work.
** Attachment added: "Example log when things fail (bug happens)."
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+attachment/5167261/+files/2018y07m24d-16h34m12s_activite_repro_1776475_je_passe_sur_session_stephane_avec_export_xdg_seat_path__org_freedesktop_displaymanager_seat0
In order to investigate this bug, I started to write down each time I
switch user and whether it works.
The time information allowed to obtain time-bounded log extracts that
focus on relevant parts using journalctl --since ... --until ... .
After 3 "work" and one "fail" case, I observed a correla
Summary: twice, bug happened when service org.gtk.vfs.Daemon is
activating *after* org.a11y.atspi.Registry is activated.
Details below.
Bug just happened again on unlocking session (versus switching users).
I compared the output of journalctl.
## Around unlock time: nothing to see
Around unloc
Sometimes a variant of the bug happens: after typing password, the
expected session does not happen. Instead, a black screen with a white
message on center, saying that session is locked and I have to wait for
a moment. About 20 seconds later, a lightdm login greeter appears and
only after typing t
So far, the logs basically show that lightdm does its job, and just does
it again when bug happens.
I have the feeling that the actual reason of the bug does not appear in
the log.
Perhaps something triggers a lock behavior, causing lightdm to just do
what it's supposed to do.
The problem might
Hello. Seen a crash report window appear on Ubuntu 16.04, mentioning
DuplicateOf https://bugs.launchpad.net/bugs/1052360 .
Also received the "unattended-upgrade" mail as usual. It said:
> Écriture du journal de dpkg dans «
> /var/log/unattended-upgrades/unattended-upgrades-dpkg.log »
> Échec de
Had the same problem as imperia777 : data intact, error message and
unable to fix it, (though no actual power failure).
Here's fsck output:
e2fsck 1.42.9 (4-Feb-2014)
myfsname: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway? yes
fsck.ext4: un
On a USB audio adapter 0d8c:000c "C-Media Electronics, Inc. Audio
Adapter", I experience same problem as original report and comment #2.
Links at comment #3 no longer exist.
I can't correlate with comment #4 and #5. To me, original report and
comment #2 only mention an annoyance on a specific vo
On re-reading the original post (which is not very clear), I'm wondering
if it's same problem.
My problem is not on VLC-specific volume in pulseaudio (or any other
app), rather on the master volume (hardware-specific).
So, perhaps it's not the same problem.
Anyway, many things have probably chan
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585282/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.l
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585283/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.l
apport information
** Attachment added: "LightdmGreeterLog.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585287/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
http
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585285/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs
apport information
** Tags added: apport-collected has-workaround regression reproducible
ubuntu
** Description changed:
# Summary
* Some glyphs badly drawn at some moments.
* When happens, same glyph drawn on various windows shows same corruption.
* Problem comes and go.
# Conte
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585284/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585286/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
http
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585288/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585295/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585294/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bu
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585296/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585299/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585297/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585289/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "NonfreeKernelModules.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585291/+files/NonfreeKernelModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585300/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585293/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585298/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585292/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585290/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bu
Hello.
Suspending then resuming system seems to have some effect.
This morning, after resume from suspend (with session still open), all
text glyphs appeared blank on the lightdm screen.
I expected the session to be fully unusable, but surprisingly, the
session itself has had no problem at all s
@penalvch this goes into complications.
Actually, I've been using 16.04 and Intel driver because in 14.10, 15.04
and 15.10, all solutions (open-source nouveau driver, open-source intel
driver and proprietary nVidia driver) have had different problems (but
not this problem).
--
You received this
I'll try that BIOS test.
In the meantime I thought I'd try again nVidia proprietary driver.
Installation of package was requested through Ubuntu driver selection
GUI.
Resulted in 2 new bugs automatically notified and reported:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1552108
https
Hi.
Same problem here. Some partitions still appear in `mount` output and
`/proc/mounts` but can't be unmounted via either device name or mount point.
Repeatedly trying `umount -l` with device names and mount points finally
managed to get the partitions unmounted.
Yet it feels awkward, like a
Summary: on reinstall on same CPU/motherboard/etc (only storage
changed), bug no longer observed.
Hello,
After observing problems on the main storage of the laptop where the bug
was observed, I bought a new storage and installed Ubuntu 16.04 from
scratch on the new storage but the same laptop.
S
Regarding new bug, subscribed to
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1568604 . Will notify if I still observed this bug (1547077).
I don't understand why this bug no longer happens (which is good
anyway).
xserver-xorg-video-nouveau is still 1:1.0.12-1build2
P
The bug is still triggered (not always) by suspend-to-ram then wake-up.
This make a frustrating user experience since the most affordable
workaround is to close the session the reopen it when bug occurs. Since
many applications are defaced (see screenshots), the user cannot
properly check if thei
Thank you Nuno for reporting the trouble you observed. I'm the one who
posted this very bug report where you added your comment.
I can understand your frustration. I'm frustrated too. I'm using open-
source nouveau driver instead and it has problems, too cf.
https://bugs.launchpad.net/ubuntu/+s
** Summary changed:
- Some glyphs drawn consistently wrong, bug comes and go
+ Suspend to ram causes some glyphs to draw consistently wrong or even appear
blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
--
You received this bug notification because you are a member of Ubuntu
Touch
@gr-ubuntu-0 thanks for reporting, it looks like it's the same issue
indeed.
@gr-ubuntu-0 can you mark the bug as affecting you? It is important for
confirmation and prioritization.
Christopher wrote:
> #53 gouri, could you please provide the bugzilla number for the report
y
Thanks again @gr-ubuntu-0 . This is interesting. Indeed your XorgLog.txt
does not mention nouveau, only Intel.
My xorg.log mentions both.
Following https://askubuntu.com/questions/23238/how-can-i-find-what-
video-driver-is-in-use-on-my-system it looks like I'm really using
nouveau driver.
LC_ALL
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574615/+files/2016y02m05d_15h50m04s_0100Z_firefox_display_bug_major_stackoverflow.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
Public bug reported:
# Summary
* Some glyphs badly drawn at some moments.
* When happens, same glyph drawn on various windows shows same corruption.
* Problem comes and go.
# Context
Laptop, using Intel driver.
Expected: all glyphs rendered correctly.
Observed: some glyphs not rendered correc
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574619/+files/2016y02m10d_18h43m35s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_03.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574617/+files/2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574616/+files/2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574618/+files/2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574621/+files/2016y02m10d_18h42m34s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_02.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574624/+files/2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574626/+files/2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whic
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574627/+files/2016y02m15d_13h16m33s_0100Z_bug_affects_superswitcher_terminal_and_more.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574625/+files/2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574629/+files/2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574628/+files/2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574630/+files/2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Oops, it looks like putting a short description obscures the attachment
names. You can hover the links with your mouse to see file names.
I'm willing to run other apps, but bug only appears after a while.
Logging out then in cures the bug.
The bug sometimes disappears on its own (it has currentl
** Description changed:
# Summary
* Some glyphs badly drawn at some moments.
* When happens, same glyph drawn on various windows shows same corruption.
* Problem comes and go.
# Context
Laptop, using Intel driver.
Expected: all glyphs rendered correctly.
Observed: so
Summary: trying proprietary nVidia driver as a workaround does not work.
I tried again to switch to nvidia-driver using GUI tool software-
properties-gtk
This caused again nvidia driver installation failure.
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1553554
Last
Laptop stickers show: nVidia GeForce GTX 850M and lspci shows both
nVidia and Intel graphics.
I'm not quite sure if nouveau or intel driver is used.
egrep '(intel|nouveau)' -i Xorg.0.log -o | sort | uniq -c
62 intel
9 Intel
1 INTEL
12 nouveau
2 NOUVEAU
Can anyone tel
Summary: trying proprietary nVidia driver as a workaround does not work.
I tried again to switch to nvidia-driver using GUI tool software-
properties-gtk
This caused again nvidia driver installation failure.
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1553554
Last
As requested by @penalvch, checked what the BIOS offers.
Answer: the BIOS does not offer to disable any intel or nividia chip.
In "Graphics Configuration", the BIOS only offers "DVMT Pre-Allocated"
with values 64M 128M 256M 512M, currently set to default 64M.
--
You received this bug notificati
Nouveau driver seems active according to dmesg.
[0.721176] nouveau :01:00.0: NVIDIA GM107 (117110a2)
[0.747014] nouveau :01:00.0: bios: version 82.07.2a.00.17
[0.856760] nouveau :01:00.0: fb: 4096 MiB DDR3
[0.856814] nouveau :01:00.0: priv: HUB0: 10ecc0 (1b
Still occurs with latest build
xserver-xorg-video-nouveau 1:1.0.12-1build2
*Bug is severely impacting for daily work.*
Strangely enough, video worked rather well with 14.10 and 15.04, we
mainly had trouble with NetworkManager there.
After using Ubuntu more than 10 years now (first was pr
After another failed attempt at installing nVidia driver through
software-properties-gtk here is another bug report
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1556960
So bugs happens every few days.
Hypothesis: bug happens when another X server is run. This happe
Hello Christopher @penalvch.
> Could you please report this problem through the appropriate channel
by following the instructions verbatim at
http://nouveau.freedesktop.org/wiki/Bugs/ ?
I performed part of it. The situation passed the "TroubleShooting" step.
I checked on the bugzilla, visited #no
Public bug reported:
# Context
I've been using /usr/bin/script quite a lot for about 4 years (since
about Ubuntu 12.04, maybe before). It always worked without problem.
I'm using several script instance most of the time, in several
terminals.
Reproducible: randomly, once every few days.
Proble
Unfortunately, the bug occurred again a few minutes ago.
This means that uninstalling light-locker and using xscreensaver instead
is not enough to prevent the bug from occurring.
AFAIK, doing so avoids light-locker creating possibly short-lived X
servers (for the purpose of asking password for un
kill -TERM does not affect runaway /usr/bin/script
kill -HUP stops it instantly
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1558236
Title:
script freezes and eats al
Confirmed that bug only happens on Ubuntu 16.04, not on previous Ubuntu
releases and not on Debian 8.3.
Machine has these OSes and can boot any at will, in case it helps:
Debian stable (8.3), Xubuntu 16.04, Xubuntu 15.04, Linux Mint 17.2
(based on Ubuntu 14.04), Fedora 23 XFCE Edition.
** Summar
## Status
Bug still occurs every few days, when I use Ubuntu 16.04, not when using
others.
## Trying to get more precise info
### Location in source code
Following https://wiki.ubuntu.com/DebuggingProgramCrash I could get an
interactive gdb prompt showing that it's blocked in the while loop
bel
# Workaround? Tried once, works.
TL;DR: reading the slave pts from another process unfreezes and allows
continued operation
cd /proc/24621/fd
ls -al
total 0
dr-x-- 2 stephane stephane 0 avril 5 16:39 .
dr-xr-xr-x 9 stephane stephane 0 avril 5 15:13 ..
lrwx-- 1 stephane stephane
# Reproducible? Tried once, takes about an hour.
This was enough to reproduce the bug once within about one hour :
open a terminal, type:
script
then on the shell prompt type:
yes
The 'yes' command produces as intended an infinite stream of lines with
the character 'y'.
After about one hour,
# Confirmed that the workaround works in practice.
I had a hang, figured out which /usr/bin/script process was eating the
CPU, then issued:
head -n 1 /proc/7514/fd/4
and it continued working.
# Try to figure out what happens.
Below is after the problem was fixed (things worked well again, the
# Summary
Bug hit again, workaround works again, this time with a strace.
I suspect the workaround has a drawback: the characters it eats are lost for
the script.
Next time I'll try dd to "lose" only one character.
Thank you for your attention.
# Details
The bug has hit again.
Here is a selec
# Summary
Bug hit again, workaround works again, this time with a strace.
I suspect the workaround has a drawback: the characters it eats are lost for
the script.
Next time I'll try dd to "lose" only one character.
Thank you for your attention.
# Details
The bug has hit again.
Here is a selec
TL;DR: Bug happened again, workaround works.
Have not tried dd yet, but whenever the bug happen I open a shell, use
bash Ctrl-R to find the one-liner below, press enter and expect that it
works around the bug.
for PROCESSLINE in $( grep -a ^script /proc/*/cmdline -l ) ; do cd
$(dirname $PROCESSLI
Public bug reported:
Was installing opencv-dev with aptitude.
Aptitude offered to resolve a conflict between libjpeg packages.
I accepted the offered solution.
Next time I opened aptitude, it sad opencv-dev packaged were not fully
installed.
Seems like error is permanent (i.e. will not resolve
apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
libopencv-highgui-dev : Depends: libjpeg-dev
libtiff5-dev : Depends: l
I tried this:
dpkg --purge libjpeg9-dev:amd64
(Reading database ... 255624 files and directories currently installed.)
Removing libjpeg9-dev:amd64 (1:9b-1) ...
but it did not completely fixed.
By making sure both libjpeg-turbo8-dev:amd64 and libjpeg8-dev:amd64 were
selected, then it seemed to f
Public bug reported:
# Context
Selecting nvidia driver using software-properties-gtk.
Install goes ok. No longer observing bug
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1553554
Hardware is Asus n551jk laptop. nvidia driver worked on same hardware
with Ubuntu 14.
Public bug reported:
On an Asus laptop running a freshly installed Ubuntu 15.04 64-bit, nm-
applet shows that NetworkManager wants to manage vboxnet0 and vboxnet1.
These are created by virtualbox which runs some guest OS inside a VM. On
previous Ubuntu releases, network-manager did not try to mana
I tried this variant to tell NetworkManager to ignore the virtual
devices:
[keyfile]
unmanaged-devices=mac:xx:xx:xx:xx:xx:xx
(using the real MAC address of course)
It still does not change anything.
But I noticed this in the log, which happen whether or not the
unmanaged-devices option is set:
I unchecked the auto-connect option on connection 'Auto SG IP auto' to
see if it changes anything.
The behavior is different but satisfying.
Again, on suspend of the host, NetworkManager disables vboxnet0.
It just does not do DHCP on it.
Again, suspending the resuming the virtual machine repairs
Oops I sent "The behavior is different but satisfying."
It meant: "The behavior is different but not satisfying."
Summary: somehow NetworkManager has very well understood (as shown in
log) that vboxnet* interfaces should be ignored, but somehow it still
manages them.
--
You received this bug no
I tried to move away all connections in /etc/NetworkManager/system-connections/
then restart network-manager, just in case configuration somehow confused it.
Problem still happens.
Thank you for your attention.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Summary: more trouble, nm-applet menu starts to fill with irrelevant
vboxnet0 entries.
Details
Now nm-applet shows 5 "vboxnet0" ethernet connections, though I've not
created any of them. 4 of them show ipv4 parameters "disabled", ipv6
parameters "ignore". Only the currently auto-activated one sho
Hello simionbcn.
Thank you for your participation. Can you elaborate ? Several setups
were discussed, we can't guess what is yours.
What is your filesystem setup ? Your version of Ubuntu, of involved packages ?
What steps have you performed ?
Such information helps a lot.
Thanks.
--
You recei
Thank you simonbcn for these interesting additions (not saying I can do
anything about it, but a nautilus developer may pick that as valuable
hints about what's wrong).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 i
> Sorry for not answering again. Are there any news on this issue?
No news. As written above, I provided users a workaround with a
.xsession. That workaround was so effective that I even forgot this bug.
> Did you already upgrade to 14.04 or do you plan to do so?
It is planned and we already kno
The error message:
* is reproducible always,
* on trusty
* with zenity, abiword, gitg, gnome-calculator, probably with other or even all
gtk3-apps, too. I have tested only a handful and all exhibit this behavior.
Zenity is mentioned in bug #1326099 .
For example:
** (zenity:10455): WARNING **:
99 matches
Mail list logo
