May 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 867068] Incorrect console settings when installing xen guest
by bugzilla_noreply＠novell.com 01 May '15

01 May '15

http://bugzilla.suse.com/show_bug.cgi?id=867068 --- Comment #4 from Charles Arnold <carnold(a)suse.com> --- I would also be useful if you could attach your config file for the domU that fails to allow input. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 923387] New: Wireless doesn't stay connected in hotels
by bugzilla_noreply＠novell.com 01 May '15

01 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=923387 Bug ID: 923387 Summary: Wireless doesn't stay connected in hotels Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: munguanaweza(a)netzero.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0 Build Identifier: The wireless system doesn't stay connected in various hotels around the world. In some hotels, there is no problem and the wireless will stay connected. In most hotels, the opensuse wireless will be cut off from the hotel wireless network withing about 10 minutes. The only way to get it to reconnect is to restart the operating system for about another 10 minutes of connection. While the opensuse wireless is connected, the wireless transfer rate of bytes/sec gets slower and slower. To contrast this with windows, it will remain connected without problem indefinitely. Windows also will not slow down its bytes/sec transfer rate over time, and the general transfer rate is higher in windows than in opensuse. I have had this issue on two different laptops, using opensuse 12.1 through 13.2. I compare these opensuse versions to both windows 7 and 8 on these two laptops. I am writing this from the hotel Pullman Bercy in Paris, France, where I am having this issue. But please don't think that this is just an isolated incident, I have this issue in hotels all over the world. I travel for a living and find this problem in hotels all over the world for several years running. I have tried to resolve this various times on the opensuse mailing list, and also have tried to work with various hotel tech support services to find a clue to resolve this, without success. Many of the hotels that I stay in while travelling used to have wired connections and I was able to bypass the wireless problem, but they have been gradually eliminated in favor of wireless systems and this problem has become a major issue and a great annoyance. I would very much appreciate if you could fix this problem! Reproducible: Always Steps to Reproduce: 1.Start up the computer 2.Connect to the hotel network 3. Soon the wireless connection will reduce to no transfer of data. Actual Results: I couldn't continue using opensuse to connect to the internet, and I have to switch to windows. Expected Results: I should have been able to stay connected to the internet via opensuse wifi without issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 922529] fails to find eMMC during initial install
by bugzilla_noreply＠novell.com 01 May '15

01 May '15

http://bugzilla.suse.com/show_bug.cgi?id=922529 --- Comment #58 from Gerry Gavigan <gerrysw11(a)gmail.com> --- Created attachment 633049 --> http://bugzilla.suse.com/attachment.cgi?id=633049&action=edit new yast2 logs with modified kernel parameters -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 922529] fails to find eMMC during initial install
by bugzilla_noreply＠novell.com 01 May '15

01 May '15

http://bugzilla.suse.com/show_bug.cgi?id=922529 Gerry Gavigan <gerrysw11(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(gerrysw11(a)gmail.c | |om) | --- Comment #57 from Gerry Gavigan <gerrysw11(a)gmail.com> --- In the absence of a better idea I removed "quiet" and added "rdshell rdinitdebug" to the kernel command line - yast logs attached -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 867068] Incorrect console settings when installing xen guest
by bugzilla_noreply＠novell.com 01 May '15

01 May '15

http://bugzilla.suse.com/show_bug.cgi?id=867068 Charles Arnold <carnold(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse(a)aastral.net Flags| |needinfo?(suse(a)aastral.net) --- Comment #3 from Charles Arnold <carnold(a)suse.com> --- (In reply to Bill Weidman from comment #0) Sorry for the very slow response. If this issue still matters to you see the inlined comments below. > User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) > AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.90 Safari/537.1 > > Xen 13.1 domU guest console is inaccessible immediately after installation. > > Reproducible: Always > > Steps to Reproduce: > 1. Install 13.1 x86_64 domU in Xen 13.1 x86_64 dom0 > 2. Shut down guest > 3. Change config files to boot using pygrub This is done automatically when you use vm-install to install a para-virtualized VM. How are you installing the domU? > 4. Boot guest > 5. Connect to console in dom0 "xl console guestname" Connecting works for me after installing using vm-install. See more info below. > > Actual Results: > Console doesn't accept input > > linux-wo1f login: root > [ 50.844129] tty_ldisc_hangup_halt: waiting (login) for xvc0 took too > long, but we keep waiting... > > Expected Results: > Xen guest console accepts inputs when connected to in dom0 > > Looks like a yast installation problem > > To fix I did the following. Not sure if this is the best way to fix, but > this is how I did it. > > Add console=xvc0 to /boot/grub/menu.lst > kernel /boot/vmlinuz-3.11.10-7-xen root=/dev/xvda2 resume=/dev/xvda1 > splash=0 console=xvc0 showopts The installed PV domU already has the /dev/xvc0 device without adding this to menu.lst. > > Then echo "xvc0" >> /etc/securetty This is done automatically by the installation (for PV domUs). It also adds in the /etc/inittab file the following line, x0:12345:respawn:/sbin/agetty -L 9600 xvc0 xterm Are you using some special autoyast file when installing your domUs that bypass this? > > Then > ln -s '/usr/lib/systemd/system/getty@.service' > '/etc/systemd/system/getty.target.wants/getty(a)xvc0.service' I've never had to do this. I again wonder how you installed the domU? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 926862] Shotwell hangs on startup
by bugzilla_noreply＠novell.com 01 May '15

01 May '15

http://bugzilla.novell.com/show_bug.cgi?id=926862 --- Comment #8 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (926862) was mentioned in https://build.opensuse.org/request/show/304927 Factory / libgphoto2 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 926862] Shotwell hangs on startup
by bugzilla_noreply＠novell.com 01 May '15

01 May '15

http://bugzilla.suse.com/show_bug.cgi?id=926862 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Marcus Meissner <meissner(a)suse.com> --- submitted a fix for factory -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 926862] Shotwell hangs on startup
by bugzilla_noreply＠novell.com 01 May '15

01 May '15

http://bugzilla.suse.com/show_bug.cgi?id=926862 --- Comment #6 from Marcus Meissner <meissner(a)suse.com> --- I debugged this a while ago and it is very tricky ;) Basically: libgphoto2 loads and unloads its usb drivers. one of them is the usb0 driver. The usb0 driver on load starts a pthread to communicate with udev. on tear down, it tries to kill this thread again, but as this happens in "dlclose()" the thread cannot terminate due to a deadlock. After debugging the best way is probably to no longer build the old libusb 0 driver anymore, as the libusb 1 driver works nicely. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 926862] New: Shotwell hangs on startup
by bugzilla_noreply＠novell.com 01 May '15

01 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=926862 Bug ID: 926862 Summary: Shotwell hangs on startup Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: delder(a)novacoast.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Ever since the upgrade to shotwell-0.22.0-1.1, I can't get shotwell to ever startup correctly. I have a largish photo/video collection (~ 195 GB) but even if I start with a new user account, shotwell will hang. From my account if I run SHOTWELL_LOG=1 shotwell I get: L 26148 2015-04-12 21:05:19 [MSG] main.vala:385: Shotwell Photo Manager 0.22.0 L 26148 2015-04-12 21:05:20 [DBG] Plugins.vala:316: Searching /home/delder/.gnome2/shotwell/plugins for plugins ... L 26148 2015-04-12 21:05:20 [DBG] Plugins.vala:135: Unable to search directory /home/delder/.gnome2/shotwell/plugins for plugins: No such file or directory L 26148 2015-04-12 21:05:20 [DBG] Plugins.vala:316: Searching /usr/lib64/shotwell/plugins for plugins ... L 26148 2015-04-12 21:05:20 [DBG] Plugins.vala:316: Searching /usr/lib64/shotwell/plugins/builtin for plugins ... L 26148 2015-04-12 21:05:20 [DBG] Plugins.vala:424: Loaded SPIT module "Core Data Import Services 0.22.0" (org.yorba.shotwell.data_imports.core_services) [/usr/lib64/shotwell/plugins/builtin/shotwell-data-imports.so] L 26148 2015-04-12 21:05:20 [DBG] Plugins.vala:424: Loaded SPIT module "Shotwell Extra Publishing Services 0.22.0" (org.yorba.shotwell.publishing.extras) [/usr/lib64/shotwell/plugins/builtin/shotwell-publishing-extras.so] L 26148 2015-04-12 21:05:20 [DBG] Plugins.vala:424: Loaded SPIT module "Core Publishing Services 0.22.0" (org.yorba.shotwell.publishing.core_services) [/usr/lib64/shotwell/plugins/builtin/shotwell-publishing.so] L 26148 2015-04-12 21:05:20 [DBG] Plugins.vala:424: Loaded SPIT module "Core Slideshow Transitions 0.22.0" (org.yorba.shotwell.transitions) [/usr/lib64/shotwell/plugins/builtin/shotwell-transitions.so] L 26148 2015-04-12 21:05:20 [MSG] main.vala:43: Verifying database ... L 26148 2015-04-12 21:05:20 [DBG] Db.vala:40: Database schema version 20 created by app version 0.20.1 L 26148 2015-04-12 21:05:20 [DBG] util.vala:171: next step: LibraryPhoto.init (0/38568) L 26148 2015-04-12 21:05:20 [DBG] util.vala:171: next step: Video.init (32999/38568) L 26148 2015-04-12 21:05:20 [MSG] VideoSupport.vala:380: interpreter state has changed; video thumbnails may be out of date L 26148 2015-04-12 21:05:20 [DBG] util.vala:171: next step: Upgrades.execute (34693/38568) L 26148 2015-04-12 21:05:20 [DBG] Upgrades.vala:85: Could not delete mimics: /home/delder/.local/share/shotwell/mimics is not a directory L 26148 2015-04-12 21:05:20 [DBG] util.vala:171: next step: Event.init (34693/38568) L 26148 2015-04-12 21:05:21 [DBG] util.vala:171: next step: Tag.init (38552/38568) L 26148 2015-04-12 21:05:21 [DBG] util.vala:171: next step: LibraryWindow (38564/38568) L 26148 2015-04-12 21:05:23 [DBG] ConfigurationInterfaces.vala:331: ConfigurationFacade: engine reports property 'DISPLAY_BASIC_PROPERTIES' changed. L 26148 2015-04-12 21:05:23 [DBG] ConfigurationInterfaces.vala:331: ConfigurationFacade: engine reports property 'DISPLAY_SEARCH_BAR' changed. L 26148 2015-04-12 21:05:23 [DBG] ConfigurationInterfaces.vala:331: ConfigurationFacade: engine reports property 'EVENTS_SORT_ASCENDING' changed. L 26148 2015-04-12 21:05:25 [DBG] LibraryWindow.vala:260: on_library_monitor_installed: /home/delder/Photos L 26148 2015-04-12 21:05:25 [DBG] util.vala:171: next step: done (38564/38568) L 26148 2015-04-12 21:05:25 [DBG] ConfigurationInterfaces.vala:331: ConfigurationFacade: engine reports property 'DISPLAY_SIDEBAR' changed. L 26148 2015-04-12 21:05:25 [DBG] ConfigurationInterfaces.vala:331: ConfigurationFacade: engine reports property 'SHOW_WELCOME_DIALOG' changed. L 26148 2015-04-12 21:05:25 [DBG] main.vala:195: 5.872067 seconds to Gtk.main() Nothing happens after that (no CPU usage at all) and I eventually have to kill it. If I launch it as a new user (never run shotwell before) I get to the main shotwell window with the "Welcome to Shotwell" splash screen but then it immediately hangs with .cache/shotwell/shotwell.log showing: L 29380 2015-04-12 21:09:10 [MSG] main.vala:385: Shotwell Photo Manager 0.22.0 L 29380 2015-04-12 21:09:11 [DBG] Plugins.vala:316: Searching /home/google/.gnome2/shotwell/plugins for plugins ... L 29380 2015-04-12 21:09:11 [DBG] Plugins.vala:135: Unable to search directory /home/google/.gnome2/shotwell/plugins for plugins: No such file or directory L 29380 2015-04-12 21:09:11 [DBG] Plugins.vala:316: Searching /usr/lib64/shotwell/plugins for plugins ... L 29380 2015-04-12 21:09:11 [DBG] Plugins.vala:316: Searching /usr/lib64/shotwell/plugins/builtin for plugins ... L 29380 2015-04-12 21:09:11 [DBG] Plugins.vala:424: Loaded SPIT module "Core Data Import Services 0.22.0" (org.yorba.shotwell.data_imports.core_services) [/usr/lib64/shotwell/plugins/builtin/shotwell-data-imports.so] L 29380 2015-04-12 21:09:11 [DBG] Plugins.vala:424: Loaded SPIT module "Shotwell Extra Publishing Services 0.22.0" (org.yorba.shotwell.publishing.extras) [/usr/lib64/shotwell/plugins/builtin/shotwell-publishing-extras.so] L 29380 2015-04-12 21:09:11 [DBG] Plugins.vala:424: Loaded SPIT module "Core Publishing Services 0.22.0" (org.yorba.shotwell.publishing.core_services) [/usr/lib64/shotwell/plugins/builtin/shotwell-publishing.so] L 29380 2015-04-12 21:09:11 [DBG] Plugins.vala:424: Loaded SPIT module "Core Slideshow Transitions 0.22.0" (org.yorba.shotwell.transitions) [/usr/lib64/shotwell/plugins/builtin/shotwell-transitions.so] L 29380 2015-04-12 21:09:11 [MSG] main.vala:43: Verifying database ... L 29380 2015-04-12 21:09:11 [DBG] Db.vala:44: Creating database schema version 20 for app version 0.22.0 L 29380 2015-04-12 21:09:13 [MSG] VideoSupport.vala:377: interpreter state cookie not found; assuming all video thumbnails are out of date L 29380 2015-04-12 21:09:13 [DBG] Upgrades.vala:85: Could not delete mimics: /home/google/.local/share/shotwell/mimics is not a directory L 29380 2015-04-12 21:09:13 [DBG] ConfigurationInterfaces.vala:331: ConfigurationFacade: engine reports property 'DISPLAY_BASIC_PROPERTIES' changed. L 29380 2015-04-12 21:09:13 [DBG] ConfigurationInterfaces.vala:331: ConfigurationFacade: engine reports property 'EVENTS_SORT_ASCENDING' changed. L 29380 2015-04-12 21:09:13 [DBG] LibraryWindow.vala:260: on_library_monitor_installed: /home/google/Pictures L 29380 2015-04-12 21:09:13 [DBG] ConfigurationInterfaces.vala:331: ConfigurationFacade: engine reports property 'DISPLAY_SIDEBAR' changed. L 29380 2015-04-12 21:09:13 [DBG] DataImportsPluginHost.vala:429: DataImportsDialog: discovered 1 pluggable data import services. L 29380 2015-04-12 21:09:13 [DBG] DataImportsPluginHost.vala:444: DataImportsDialog: discovered pluggable data import service 'F-Spot'. L 29380 2015-04-12 21:09:13 [DBG] FSpotImporter.vala:328: FSpotDataImporter instantiated. L 29380 2015-04-12 21:09:13 [DBG] DataImportsPluginHost.vala:268: WelcomeDataImportsHost.start_importing( ): invoked. L 29380 2015-04-12 21:09:13 [DBG] FSpotImporter.vala:345: FSpotDataImporter: starting interaction. L 29380 2015-04-12 21:09:13 [DBG] DataImportsPluginHost.vala:322: WelcomeDataImportsHost: Installing library selection pane for F-Spot I'm running the latest (as of 20150425) version of Tumbleweed and have never seen this problem in older versions (0.21 and lower). -- You are receiving this mail because: You are on the CC list for the bug.

1 6