Not sure what causes the problem or how to fix it manually but a reboot
cleared it up for me (same exact error message from terminal as original
reporter). So after reboot it is working fine again. This is Ubuntu
16.04, btw.
--
You received this bug notification because you are a member of
The fix from the fourdollars ppa is also working for me: Lenovo x230.
I ran the stress test before applying the fix and confirmed that wifi
was non-functioning after the 30 suspend / wake cycles and needed the
"sudo wpa_cli scan" to activate it again.
I then added the ppa and applied the update
@fourdollars does this commit get applied to 16.04 proposed and then to
backports? I (and I am sure others) would be happy to test this for
xenial but I am unclear as to the path the patches follow to get to the
main repositories.
--
You received this bug notification because you are a member
As reported at Bug #1340161 the problem is solved for a Canon LiDE 110
scanner using Ubuntu 16.04 and simple-scan 3.20.0=0ubuntu1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
*** This bug is a duplicate of bug 1327801 ***
https://bugs.launchpad.net/bugs/1327801
Brightness and Contrast adjustments for Canon LiDE 110 in Ubuntu 16.04,
simple-scan 3.20.0-0ubuntu1 work perfectly! So I think this specific
bug is solved, even though others with different scanner models
*** This bug is a duplicate of bug 1449112 ***
https://bugs.launchpad.net/bugs/1449112
CzBiX can you clarify your patch? It works but I am having trouble
following the logic.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0
I haven't found out how to set XDG_CURRENT_DESKTOP from mdm (Linux
Mint's fork of older gdm), so then when attempting to login to Gnome-
Shell I am greeted with a black screen. However, doing this is a
workaround (but still leaves XDG_CURRENT_DESTKOP unset):
in
@romano-giannetti I see now that you indicate you are not using lightdm.
Can you confirm your login manager? If so we may have a different
problem, but everything else seems identical.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I also have this problem and if it is the same bug I have narrowed it
down to lightdm.
I am using Mint 17 (based on Ubuntu 14.04). Mint's default login
manager is mdm (fork of gdm). With it, usb devices are auto-mounted
just fine when plugged in.
When I install lightdm and choose it as the
This is affecting me also with a Huawei E1690 modem. It will be found
by Network Manager only on even plug-ins (so, not found on 1st, 3rd,
5th plugins, but found on 2nd, 4th, 6th plugins). This is with Ubuntu
14.04 up-to-date as of 13 Feb, 2014.
--
You received this bug notification because
Forgot to note that this E1690 Modem was working fine in Ubuntu 12.04
(same machine). This is a bit older modem and starts as 12d1:1446,
and is switched by usb-modeswitch to: 12d1:1001 (not the 12d1:1436 that
ivano mentions for newer Huawei modems).
UPDATE: OK, now it seems to be showing every
UPDATE: I stand corrected. This E1690 modem is not mode-switched the
FIRST time connected to the machine. Watching lsusb, the device just
stays at its original ID of 12d1:1446 and never switches to 12d1:1001.
But if I unplug it and replug it, the 2nd, 3rd, 4th, times it is always
correctly
I enabled usb-modeswitch logging in /etc/usb_modeswitch.conf, and tried
again. After rebooting, the first plugin of the device (where it is not
switched generates no log by usb-modeswitch at
/var/log/usb_modeswitch*). The second plugin does generate a log,
/var/log/usb_modeswitch.log).
So, it
I have downloaded and installed trusty 64 daily build (2013-01-07) on a
real partition on the Toshiba Tecra M10 machine used to originally
report this problem (so no variable to it being a VM or running from a
LiveCD).
When connecting an external monitor via VGA (after machine already
running),
@penalvch I added the edgers PPA, performed a dist-upgrade, rebooted,
and still have the same results: hot plugging the monitor after
already booted without it has it show correctly in Displays but there
is *no* signal sent to the monitor. Only upon reboot does it receive
the signal correctly.
I have since clarified that problem 2 from comment #4 above is not
valid, and was related to the specific application we were using.
So, in summary, there does NOT seem to be any issue with setting ibus as
the keyboard input method in Language Support.
But, problem 1 from comment #4 above
Sorry for the double post above in comments 12 and 13. Björn is correct
this does NOT seem LibreOffice related.
I have since clarified that problem 2 from comment #13 above is not
valid, and was related to the specific application we were using.
So, in summary, there does NOT seem to be any
17 matches
Mail list logo
