October 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 937067] New: efi=1 does not seem to work anymore
by bugzilla_noreply＠novell.com 17 Dec '21

17 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=937067 Bug ID: 937067 Summary: efi=1 does not seem to work anymore Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: kukuk(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- In the past, you could add efi=1 as argument for the installer, and your system was setup for EFI boot, even if the detection fails. This works only partly with Tumbleweed 20150630: the bootloader still installs and configures grub2-x86_64-efi, but the storage proposal does not create a vfat /boot/EFI partition anymore. This works with SLES12, haven't tested openSUSE 13.2. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 929755] New: shutter is missing perl(Gnome2) in Tumbleweed
by bugzilla_noreply＠novell.com 21 Nov '21

21 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=929755 Bug ID: 929755 Summary: shutter is missing perl(Gnome2) in Tumbleweed Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: f_koch(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36 Build Identifier: flo@linux-mvsa:~> sudo zypper in shutter Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides perl(Gnome2) needed by shutter-0.93.1-1.1.noarch Solution 1: do not install shutter-0.93.1-1.1.noarch Solution 2: break shutter-0.93.1-1.1.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 930505] New: every package available in standard or optional repos is not discoverable via https://software.opensuse.org/search
by bugzilla_noreply＠novell.com 06 Oct '21

06 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=930505 Bug ID: 930505 Summary: every package available in standard or optional repos is not discoverable via https://software.opensuse.org/search Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Infrastructure Assignee: mrueckert(a)suse.com Reporter: mrmazda(a)earthlink.net QA Contact: lrupp(a)suse.com Found By: --- Blocker: --- mc is the package name and binary executable for the best available file manager in openSUSE repos. Latest Midnight Commander (mc) not discoverable via https://software.opensuse.org/search . Until recently, current mc for 13.1 could be found on http://download.opensuse.org/repositories/Base:/System/openSUSE_13.2/ but this repo has been retired. Searching https://software.opensuse.org/search for search term commander produces no hits for Midnight Commander or mc. Search term mc is not acceptable to https://software.opensuse.org/search, as it rejects two character search strings, first by announcement, then when proceeding anyway, searching for mc only as a substring, listing many packages containing string mc but not mc itself. I tried searching for latest mc on https://build.opensuse.org/search but as I am not a builder I found it too difficult to use to locate latest (mc-4.8.14) even with help from irc://freenode/opensuse-factory. Something needs to be done so that every package that exists in standard or BS repos can be discovered via https://software.opensuse.org/search without the degree of difficulty searching for Midnight Commander presents. -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 952288] New: Find a way to set Adwaita as systemwide icon theme when installing GNOME DE
by bugzilla_noreply＠novell.com 28 Sep '21

28 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=952288 Bug ID: 952288 Summary: Find a way to set Adwaita as systemwide icon theme when installing GNOME DE Classification: openSUSE Product: openSUSE Factory Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: zaitor(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- As of today, any user installing GNOME as DE will still end up with DMZ set as system cursor instead of Adwaita. (do a grep X_MOUSE_CURSOR /etc/sysconfig/windowmanager on your boxes). Now this is only noticed when users open up yast (and possibly odd 3'rd party apps) It's rather visually unpleasing, and something we should look into fixing. The easiest thing to do would probably be to add it to one of our branding packages, or even create a new one if needed. Ideally we should offer a "system option" in tweak tool, but that will probably be a lot of work. Patches/fixes welcome everyone. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 902583] New: Thunderbird fails to connect when launched before Internet connection is up
by bugzilla_noreply＠novell.com 09 Sep '21

09 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=902583 Bug ID: 902583 Summary: Thunderbird fails to connect when launched before Internet connection is up Classification: openSUSE Product: openSUSE Distribution Version: 13.2 RC 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: sb56637(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, I have noticed that if I launch Thunderbird before my network connection is up (NetworkManager WiFI connection), it will fail to connect even after the network comes up. The only way to make it connect is by closing all instances and restarting Thunderbird. This appears to be related to Bug 90258. Thanks for looking into this! -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 909111] New: The rescan-scsi-bus.sh from the sgutils package is broken since SuSE-13.1
by bugzilla_noreply＠novell.com 26 Aug '21

26 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=909111 Bug ID: 909111 Summary: The rescan-scsi-bus.sh from the sgutils package is broken since SuSE-13.1 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dmarkh(a)cfl.rr.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 Build Identifier: This script no longer "finds new" or "removes no longer attached" scsi devices. As shown below, I have a scsi disk at scsi ID-0 at /dev/sg5. # lsscsi -g [0:0:0:0] disk ATA ST3320620AS K /dev/sda /dev/sg0 [13:0:0:0] process Marvell 91xx Config 1.01 - /dev/sg1 [16:0:0:0] disk IMPRIMIS 94601-15 4614 /dev/sdd /dev/sg5 [17:0:0:0] cd/dvd LITE-ON DVDRW LH-20A1P KL0G /dev/sr0 /dev/sg2 [18:0:0:0] disk ATA ST3160811AS E /dev/sdb /dev/sg3 [18:0:1:0] disk ATA ST3160815AS B /dev/sdc /dev/sg4 I remove the drive at scsi ID-0 drive and install an additional drive at scsi ID-1 then run the script. # rescan-scsi-bus.sh Scanning SCSI subsystem for new devices Scanning host 0 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning for device 0 0 0 0 ... OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: ST3320620AS Rev: K Type: Direct-Access ANSI SCSI revision: 05 Scanning host 1 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 2 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 3 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 4 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 5 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 6 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 7 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 8 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 9 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 10 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 11 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 12 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 13 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning for device 13 0 0 0 ... OLD: Host: scsi13 Channel: 00 Id: 00 Lun: 00 Vendor: Marvell Model: 91xx Config Rev: 1.01 Type: Processor ANSI SCSI revision: 05 Scanning host 14 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 15 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 16 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning for device 16 0 0 0 ... OLD: Host: scsi16 Channel: 00 Id: 00 Lun: 00 Vendor: IMPRIMIS Model: 94601-15 Rev: 4614 Type: Direct-Access ANSI SCSI revision: 01 Scanning host 17 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning for device 17 0 0 0 ... OLD: Host: scsi17 Channel: 00 Id: 00 Lun: 00 Vendor: LITE-ON Model: DVDRW LH-20A1P Rev: KL0G Type: CD-ROM ANSI SCSI revision: 05 Scanning host 18 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning for device 18 0 0 0 ... OLD: Host: scsi18 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: ST3160811AS Rev: E Type: Direct-Access ANSI SCSI revision: 05 Scanning for device 18 0 1 0 ... OLD: Host: scsi18 Channel: 00 Id: 01 Lun: 00 Vendor: ATA Model: ST3160815AS Rev: B Type: Direct-Access ANSI SCSI revision: 05 0 new or changed device(s) found. 0 remapped or resized device(s) found. 0 device(s) removed. # lsscsi -g [0:0:0:0] disk ATA ST3320620AS K /dev/sda /dev/sg0 [13:0:0:0] process Marvell 91xx Config 1.01 - /dev/sg1 [16:0:0:0] disk IMPRIMIS 94601-15 4614 /dev/sdd /dev/sg5 [17:0:0:0] cd/dvd LITE-ON DVDRW LH-20A1P KL0G /dev/sr0 /dev/sg2 [18:0:0:0] disk ATA ST3160811AS E /dev/sdb /dev/sg3 [18:0:1:0] disk ATA ST3160815AS B /dev/sdc /dev/sg4 It not only did not remove the one at ID-0 that was removed, but did not find the new one attached. Below is an "lsscsi -g" after a reboot with BOTH drives attached. #lsscsi -g [0:0:0:0] disk ATA ST3320620AS K /dev/sda /dev/sg0 [13:0:0:0] process Marvell 91xx Config 1.01 - /dev/sg1 [16:0:0:0] disk IMPRIMIS 94601-15 4614 /dev/sdd /dev/sg5 [16:0:1:0] disk IMPRIMIS 94601-15 4614 /dev/sde /dev/sg6 [17:0:0:0] cd/dvd LITE-ON DVDRW LH-20A1P KL0G /dev/sr0 /dev/sg2 [18:0:0:0] disk ATA ST3160811AS E /dev/sdb /dev/sg3 [18:0:1:0] disk ATA ST3160815AS B /dev/sdc /dev/sg4 Reproducible: Always Steps to Reproduce: 1. See details 2. 3. Actual Results: This script, before SuSE-13.1 would remove any disks physically removed and add any physically added since boot. It is broken This is NOT kernel related as the same thing happens with a vanilla 3.16.7 kernel. I'm fairly certain this is a systemd issue. -- You are receiving this mail because: You are on the CC list for the bug.

2 16

[Bug 927832] New: libreoffice does not discover printers in client only mdns setup
by bugzilla_noreply＠novell.com 18 Aug '21

18 Aug '21

http://bugzilla.suse.com/show_bug.cgi?id=927832 Bug ID: 927832 Summary: libreoffice does not discover printers in client only mdns setup Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: LibreOffice Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- libreoffice only offers "Generic Printer" when run without cupsd. Printers can be discovered nevertheless using mdns and e.g. evince works fine. LO probably needs to be compiled to use the new cups 1.6 APIs: http://www.cups.org/documentation.php/doc-2.0/api-cups.html#cupsEnumDests -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 899501] New: Only one display wakes up after powersave
by bugzilla_noreply＠novell.com 03 Aug '21

03 Aug '21

http://bugzilla.suse.com/show_bug.cgi?id=899501 Bug ID: 899501 Summary: Only one display wakes up after powersave Classification: openSUSE Product: openSUSE Factory Version: 201409* Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: X.Org Assignee: bnc-team-xorg-bugs(a)forge.provo.novell.com Reporter: lmb(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 608781 --> http://bugzilla.suse.com/attachment.cgi?id=608781&action=edit Xorg.0.log I have a Lenovo Thinkpad T440s with Intel graphics. I'm using a dual monitor setup - the internal 1920x1080 display on eDP1 and a 1920x1200 screen (HP ZR24w on DP4 via the docking station). (Running Factory as of now, but tried 13.2b1 yesterday and had the same effect.) Leaving the system alone for a bit leads to the screens being turned off (powersave). However, only the internal display wakes up again; the external output remains in power-save mode. (e.g., the monitor doesn't find any signal on any port.) I tried using xrandr --output --off and turning it on with --auto again, turning off the monitor itself, etc. No change; the only apparent way to resolve this and get my external monitor back is to reboot, which seems a bit harsh. Any suggestions? 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 32767 x 32767 eDP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 309mm x 175mm 1920x1080 60.01*+ 1400x1050 59.98 1280x1024 60.02 1280x960 60.00 1024x768 60.00 800x600 60.32 56.25 640x480 59.94 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) DP3 disconnected (normal left inverted right x axis y axis) DP4 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 546mm x 352mm 1920x1200 59.95*+ 1920x1080 59.99 1600x1200 60.00 1680x1050 59.95 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1024x768 60.00 800x600 60.32 640x480 60.00 DP5 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) Pl -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 901887] New: Lenovo t440s / Intel 4400: External display non-functional
by bugzilla_noreply＠novell.com 03 Aug '21

03 Aug '21

http://bugzilla.suse.com/show_bug.cgi?id=901887 Bug ID: 901887 Summary: Lenovo t440s / Intel 4400: External display non-functional Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: X.Org Assignee: bnc-team-xorg-bugs(a)forge.provo.novell.com Reporter: lmb(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 610633 --> http://bugzilla.suse.com/attachment.cgi?id=610633&action=edit Xorg.0.log On the same system where I experienced bug 899501, I've updated the system to a later Factory build and can now no longer activate my external display at all. Though xrandr reports: Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 32767 x 32767 eDP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 309mm x 175mm 1920x1080 60.01*+ 1400x1050 59.98 1280x1024 60.02 1280x960 60.00 1024x768 60.00 800x600 60.32 56.25 640x480 59.94 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) DP3 disconnected (normal left inverted right x axis y axis) DP4 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 546mm x 352mm 1920x1200 59.95*+ 1920x1080 59.99 1600x1200 60.00 1680x1050 59.95 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1024x768 60.00 800x600 60.32 640x480 60.00 DP5 disconnected (normal left inverted right x axis y axis) The output on DP4 is black, and the monitor does not detect a signal. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 903189] New: USB trackball not detected on reboot
by bugzilla_noreply＠novell.com 03 Aug '21

03 Aug '21

http://bugzilla.suse.com/show_bug.cgi?id=903189 Bug ID: 903189 Summary: USB trackball not detected on reboot Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: lmb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 611775 --> http://bugzilla.suse.com/attachment.cgi?id=611775&action=edit lsusb -v directly after reboot After a reboot, the kernel doesn't detect the USB attached trackball automatically. I have to unplug and plug it in again. I'm attaching lsusb output directly after a reboot and after the unplug/plug step (to the same USB port). Note that it is attached to a port on the docking station. -- You are receiving this mail because: You are on the CC list for the bug.

2 2