Re: Duplicated conflicting packages after failed dnf system-upgrade from 26 to 27
> On Wed, 18 Oct 2017 09:49:07 - > Marcin Zajączkowski <mszpak(a)wp.pl wrote: > > > In the man page for yum2dnf, it lists the commands for cleanup as > follows. For your case, it is probably > > dnf repoquery --duplicated > > to find the dups. > > dnf repoquery --unsatisfied > > to find any problems. > > And > > dnf remove $(dnf repoquery --duplicated --latest-limit -1 -q) > > to remove duplicated packages. Thanks for your suggestion. I will try it as the another approach (hopefully it will not be needed) as in the meantime I removed all fc27 packages using "rpm -e $(cat list-of-fc27-packages)" to perform an update once again. However, it resulted in the fact that fc27 packages were removed (only fc26 packages remained), but applications started to complain that there is no gllibc in F26 version (only F27). "rpm -V" reports that files are corrupted. I suspect that "rpm -e" removed newer packages, but as the files were conflicted (and already upgraded to F27 at the filesystem) they remained. I needed to manually reinstall (rpm -U --force) the key packages to bring dnf to life again (e.g. issue with SSL certificated in curl). Do you think that "dnf remove" will be smarted? It would be better to make an upgrade to F27 packages (they are already downloaded and in addition can leverage system-upgrade plugin in chroot mode to do it) ignoring conflicting F26 packages and later on remove old F26 packages. Unfortunately I was able to force dnf to do that (before I manually removed old packages). Marcin ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Duplicated conflicting packages after failed dnf system-upgrade from 26 to 27
In the end yes, however, I was wondering what is the best solution to deal with conflicted packages which can occur during any interrupted dnf update session (not just during the system-upgrade). Marcin ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Duplicated conflicting packages after failed dnf system-upgrade from 26 to 27
Hello guys. I was upgrading Fedora with the system-upgrade plugin from 26 to 27. The upgrade process failed for unknown reasons (during the packages installing), my computer rebooted and I'm not able to use my Fedora :). I booted up with LiveCD, chrooted to my broken Fedora and I tried to resume the upgrade process. Unfortunately there is a lot (>200) conflicting packages (for Fedora 26 and 27). I tried to use "dnf remove --duplicated", however it would like to remove also all dependent packages. Q. What can I resume update/upgrade process having duplicated packages with DNF (install new packages and remove all)? Marcin ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Broken integration with Gnome Shell notification in Thunderbird 24
Hi, An upgrade to Thunderbird 24 (Fedora 19) broke integration with Gnome Shell notification mechanism. Currently the notification are displayed using the default Thunderbird notification mechanism instead of the Gnome Shell one (as it has worked with Gnome 3 since I remember). I wonder if it is caused by some changes in Thunderbird 24 or there is an issue with the new RPM package? Marcin -- http://blog.solidsoft.info/ - Working code is not enough -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Undetected Fresco Logic FL1000G USB 3.0 controller in Asus N43SN after replace a motherboard
On 2013-08-16 02:48, poma wrote: On 15.08.2013 22:13, Marcin Zajączkowski wrote: On 2013-08-12 19:27, poma wrote: On 12.08.2013 13:03, Marcin Zajączkowski wrote: Hi, I had no problem with a USB 3.0 port in my Asus N43SN since I bought a laptop (~2 years). Recently I replaced a motherboard to the new one (N43SL.413 looked the same as the first one) due to a problem with a graphical chipset and after that a USB3 controller stopped to be even detected. $ modinfo -F author xhci-hcd.ko Sarah Sharp http://vger.kernel.org/vger-lists.html#linux-usb Thanks for a hint. It is resolved? A pen drive in this port is not visible even in BIOS (precisely in EasyFlash tool run from BIOS). The same pen drive in a USB 2.0 port works fine. In my colleague's laptop (the same model) BIOS sees a pen drive in a USB 3.0 port, so it looks like a problem with BIOS (upgrade to the latest version didn't help) or with hardware (it worked fine in the motherboard before a replacement). I reported an another service issue to ASUS. Marcin -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Undetected Fresco Logic FL1000G USB 3.0 controller in Asus N43SN after replace a motherboard
On 2013-08-12 19:27, poma wrote: On 12.08.2013 13:03, Marcin Zajączkowski wrote: Hi, I had no problem with a USB 3.0 port in my Asus N43SN since I bought a laptop (~2 years). Recently I replaced a motherboard to the new one (N43SL.413 looked the same as the first one) due to a problem with a graphical chipset and after that a USB3 controller stopped to be even detected. $ modinfo -F author xhci-hcd.ko Sarah Sharp http://vger.kernel.org/vger-lists.html#linux-usb Thanks for a hint. Marcin -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Undetected Fresco Logic FL1000G USB 3.0 controller in Asus N43SN after replace a motherboard
Hi, I had no problem with a USB 3.0 port in my Asus N43SN since I bought a laptop (~2 years). Recently I replaced a motherboard to the new one (N43SL.413 looked the same as the first one) due to a problem with a graphical chipset and after that a USB3 controller stopped to be even detected. $ lspci | grep -i USB 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) (in the past there was also an additional USB3 controller - AFAIR Fresco Logic FL1000G USB 3.0). I though it was a problem with a motherboard, but after boot with different kernel the controller showed up. I started to suspect a bug in kernel, but after two days (I use it only from time to time with my USB3 hard drive) I noticed that USB3 port/controller is not visible anymore with any kernel. I don't know if this behavior is normal for a hardware malfunction. In /var/log/messages there is no info about the USB3 controller (see log below). I tried pci=nomsi in Grub, but with no effect. I could try to replace the mother board to the new one once again (I don't have the old one), but it could be hard to convince service that this is a problem with hardware (the port in the new motherboard worked fine twice). I don't any other OS to test it on it. Tested with kernels: kernel-3.10.4-100.fc18.x86_64 kernel-3.9.11-200.fc18.x86_64 kernel-3.9.9-201.fc18.x86_64 and in addition with System Rescue CD. What could be a reason? Can I force kernel to see it (there is no module xhci_hcd - it is built into kernel)? Marcin [1.424160] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [1.424162] ehci-pci: EHCI PCI platform driver [1.424249] ehci-pci :00:1a.0: EHCI Host Controller [1.424310] ehci-pci :00:1a.0: new USB bus registered, assigned bus number 1 [1.424327] ehci-pci :00:1a.0: debug port 2 [1.428259] ehci-pci :00:1a.0: irq 16, io mem 0xdf008000 [1.433314] ehci-pci :00:1a.0: USB 2.0 started, EHCI 1.00 [1.43] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [1.45] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.47] usb usb1: Product: EHCI Host Controller [1.49] usb usb1: Manufacturer: Linux 3.9.9-201.fc18.x86_64 ehci_hcd [1.433341] usb usb1: SerialNumber: :00:1a.0 [1.433438] hub 1-0:1.0: USB hub found [1.433442] hub 1-0:1.0: 2 ports detected [1.433581] ehci-pci :00:1d.0: EHCI Host Controller [1.433621] ehci-pci :00:1d.0: new USB bus registered, assigned bus number 2 [1.433638] ehci-pci :00:1d.0: debug port 2 [1.437561] ehci-pci :00:1d.0: irq 23, io mem 0xdf007000 [1.443310] ehci-pci :00:1d.0: USB 2.0 started, EHCI 1.00 [1.443323] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [1.443325] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.443327] usb usb2: Product: EHCI Host Controller [1.443329] usb usb2: Manufacturer: Linux 3.9.9-201.fc18.x86_64 ehci_hcd [1.443331] usb usb2: SerialNumber: :00:1d.0 [1.443414] hub 2-0:1.0: USB hub found [1.443418] hub 2-0:1.0: 2 ports detected [1.443485] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [1.443495] uhci_hcd: USB Universal Host Controller Interface driver === this part is currently missing - START === [1.443569] xhci_hcd :04:00.0: xHCI Host Controller [1.443608] xhci_hcd :04:00.0: new USB bus registered, assigned bus number 3 [1.572613] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [1.572616] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.572617] usb usb3: Product: xHCI Host Controller [1.572620] usb usb3: Manufacturer: Linux 3.9.9-201.fc18.x86_64 xhci_hcd [1.572621] usb usb3: SerialNumber: :04:00.0 [1.572706] hub 3-0:1.0: USB hub found [1.572712] hub 3-0:1.0: 1 port detected [1.572761] xhci_hcd :04:00.0: xHCI Host Controller [1.572802] xhci_hcd :04:00.0: new USB bus registered, assigned bus number 4 [1.572829] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003 [1.572831] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.572833] usb usb4: Product: xHCI Host Controller [1.572835] usb usb4: Manufacturer: Linux 3.9.9-201.fc18.x86_64 xhci_hcd [1.572837] usb usb4: SerialNumber: :04:00.0 [1.572911] hub 4-0:1.0: USB hub found [1.572916] hub 4-0:1.0: 1 port detected === this part is currently missing - END === [1.580289] usbcore: registered new interface driver usbserial [1.580295] usbcore: registered new interface driver usbserial_generic -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora
Problem with blacklisting kernel modules with boot parameter
Hi, I was playing with Fedora 16 Alpha and I've got a problem with Kernel 3.x and a camera in my laptop preventing me from installation [1]. The workaround seems to blacklist a uvcvideo kernel module, but because it's an installation process and can't just add module to /etc/modprobe.d/blacklist.conf (without a LiveCD customization). I've read about rd.blacklist boot parameter [2] which should work starting with Fedora 12 (as I understand it) [3], but in my case it doesn't. I've tried with rd.blacklist=uvcvideo and blacklist=uvcvideo at boot time, but uvcvideo is still loaded. Is there something else I've missed or this could be a bug in Fedora 16 Alpha? [1] - https://bugzilla.redhat.com/show_bug.cgi?id=734963 [2] - http://people.redhat.com/harald/dracut.html [3] - http://fedoraproject.org/wiki/Features/Dracut Regards Marcin -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Problem with blacklisting kernel modules with boot parameter
On 2011-09-02 22:06, Tom Horsley wrote: On Fri, 02 Sep 2011 21:43:53 +0200 Marcin Zajączkowski wrote: I've read about rd.blacklist boot parameter [2] which should work starting with Fedora 12 (as I understand it) [3], but in my case it doesn't. I've always seen that spelled rdblacklist (no dot). Thanks for your reply. I just tried it, but with no effect. What is more I tried to blacklist some minor module on an another computer with Fedora 14 using rd.blacklist, rdblacklist and blacklist - module was loaded all the time. Could someone confirm that blacklisting at boot level really works for him/her? Regards Marcin -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
