On 10/29/2017 01:38 PM, stakanov wrote:
In data domenica 29 ottobre 2017 20:06:02 CET, Bruce Ferrell ha scritto:
I keep removing calibre:
zypper remove
rpm -e
Every time I install a new package from yast or zypper it jumps back in AND then on the next install run tells me there unmeetable dependencies.
There is probably a package that has calibre as a depenency. You can check if you need that package (maybe it is an additional package for calibre). In case not, you can take it off and the dependency will stop to nag. If not you can as others said, taboo it in yast. Works quite well.
Any thought on how to make it go away?
Also, any thought on why with the nividia drivers installed vs nouveau, no desktop will start except failsafe?
when you install nvidia from the community repos make sure that the right driver is selected. Double check that your chipset fits the driver. When you install your driver from nvidia directly, bear in mind that every kernel update requires a re-installation of the proprietary driver.
It's a GeForce GTX 765M.
I think that's the G03 driver.
I used to deal with this as a manual install from a tarball with DKMS, but I just don't have the time to fool with it anymore. note that the prop nvidia driver will not be installed unless *you* or something you are installing calls for it and I cannot think of an app
* Bruce Ferrell <bferrell@baywinds.org> [10-29-17 17:27]: that would pull in the nvidia prop driver. somehow *you* are asking for it to be installed. AFAIU the OP did have two distinctive problems. a) calibre is called in by a dependency b) nvidia driver (which is a wanted feature for him) does not work as expected, because the community repos did install the G03 driver, but that driver, albeith it allows to log into the graphical system via the "failsafe
In data domenica 29 ottobre 2017 22:30:49 CET, Patrick Shanahan ha scritto: menu in grub" the normal login does not work. @Bruce (and please correct the above, should it be mistaken) A kernel update can cause this kind of problems. Can you check that (when you are running the "failsafe" from menu, it is actually the very same kernel you are booting and not the previous one. Another thing you can try: when you are (I suppose you run kde) in the desktop environment, go to settings kde and there you go to display. Look at AFAIR "advanced settings" and choose openGL 2.0 if 3.1 is selected. You may also try if unchecking effect does change some thing. If openGL is on 2.0 already you may try (just for the sake of it) to set it to 3.1. All this of course if I did not understand badly the above. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org