[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Xubuntu 22.04.1 after upgrading from 20.04 In order to get multiple Windows 10 systems to "discover" the samba shares on two different Xubuntu systems, I had to re-enable SMB1 protocol on all the Windows systems. Microsoft apparently keeps disabling this on system updates. As reported above, old Windows mapped drive assignments made to Ubuntu samba shares have continued to work over time, but new shares cannot be seen unless SMB1 is enabled. of course, this should all just work using newer secure protocols. For a significant piece of server software, the fact that this hasn't been addressed long ago is a real mystery. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to a duplicate bug report (1881780). https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974254] Re: Probles with Clutter
Tim, I followed your advice and yes, that fixed most of the problems I was having. Apparently there was a system update that required a reboot, but there was an error and it just said all updates applied. This has occurred on the past couple of updates that didn't have too many changes, but something clearly got screwed up. I should have done this reboot myself, but I've become too comfortable believing the package manager. I won't make that mistake again. So that appears to resolve the issue. Thanks to you and Erich for your feedback. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974254 Title: Probles with Clutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clutter-gtk/+bug/1974254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974254] Re: Probles with Clutter
I will follow up elsewhere, but I would really like to understand the disposition of clutter, given the site I reported that says it is now gone. What is actually happening here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974254 Title: Probles with Clutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clutter-gtk/+bug/1974254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974254] Re: Probles with Clutter
??? Can you be more specific. I am fully patched on 20.04.4 and I still get the same error reports from geeqie and cheese. Both worked until very recently and neither package was updated in quite some time. The developer of geeqie reported that he saw the same problem. Then he didn't! I am also finding a lot of other stable applications have stopped working such as openshot and kdenlive video editors, although these are Qt apps. Possibly there is a deeper underlying problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974254 Title: Probles with Clutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clutter-gtk/+bug/1974254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975384] Re: openshot has started crashing
I just tried to start kdenlive with similar bad results. There are so many programs failing that there must be some underlying common problem. 141-> kdenlive Icon theme "crystalsvg" not found. Icon theme "crystalsvg" not found. WARNING : Fails to parse "deinterlace" "videostab" is blacklisted "videostab2" is blacklisted "resample" is blacklisted "qtext" is blacklisted WARNING : Fails to parse "audiochannels" WARNING : Fails to parse "audioconvert" WARNING : Fails to parse "data_feed" "data_show" is blacklisted WARNING : Fails to parse "imageconvert" "mask_apply" is blacklisted "mask_start" is blacklisted "mono" is blacklisted "region" is blacklisted "resize" is blacklisted "transition" is blacklisted "watermark" is blacklisted WARNING : Fails to parse "jack" "jackrack" is blacklisted WARNING : Fails to parse "avcolour_space" WARNING : Fails to parse "avcolor_space" WARNING : Fails to parse "avdeinterlace" WARNING : Fails to parse "swscale" "avfilter.abench" is blacklisted "avfilter.acompressor" is blacklisted "avfilter.adelay" is blacklisted "avfilter.aecho" is blacklisted "avfilter.aemphasis" is blacklisted "avfilter.aeval" is blacklisted "avfilter.afade" is blacklisted "avfilter.afftfilt" is blacklisted "avfilter.agate" is blacklisted "avfilter.ametadata" is blacklisted "avfilter.arealtime" is blacklisted "avfilter.ashowinfo" is blacklisted "avfilter.channelmap" is blacklisted "avfilter.chorus" is blacklisted "avfilter.earwax" is blacklisted "avfilter.volume" is blacklisted "avfilter.volumedetect" is blacklisted "avfilter.ass" is blacklisted "avfilter.atadenoise" is blacklisted "avfilter.avgblur" is blacklisted "avfilter.bbox" is blacklisted "avfilter.bench" is blacklisted "avfilter.blackdetect" is blacklisted "avfilter.blackframe" is blacklisted "avfilter.boxblur" is blacklisted "avfilter.bwdif" is blacklisted "avfilter.chromakey" is blacklisted "avfilter.colorkey" is blacklisted "avfilter.colormatrix" is blacklisted "avfilter.colorspace" is blacklisted "avfilter.convolution" is blacklisted "avfilter.crop" is blacklisted "avfilter.cropdetect" is blacklisted "avfilter.curves" is blacklisted "avfilter.datascope" is blacklisted "avfilter.dctdnoiz" is blacklisted "avfilter.deband" is blacklisted "avfilter.deflate" is blacklisted "avfilter.deinterlace_vaapi" is blacklisted "avfilter.deshake" is blacklisted "avfilter.despill" is blacklisted "avfilter.doubleweave" is blacklisted "avfilter.drawbox" is blacklisted "avfilter.drawgraph" is blacklisted "avfilter.drawgrid" is blacklisted "avfilter.drawtext" is blacklisted "avfilter.elbg" is blacklisted "avfilter.eq" is blacklisted "avfilter.fade" is blacklisted "avfilter.field" is blacklisted "avfilter.fieldhint" is blacklisted "avfilter.fieldorder" is blacklisted "avfilter.find_rect" is blacklisted "avfilter.floodfill" is blacklisted "avfilter.fspp" is blacklisted "avfilter.gblur" is blacklisted "avfilter.geq" is blacklisted "avfilter.hflip" is blacklisted "avfilter.hqdn3d" is blacklisted "avfilter.hqx" is blacklisted "avfilter.hue" is blacklisted "avfilter.hwdownload" is blacklisted "avfilter.idet" is blacklisted "avfilter.il" is blacklisted "avfilter.lenscorrection" is blacklisted "avfilter.loop" is blacklisted "avfilter.lumakey" is blacklisted "avfilter.lut" is blacklisted "avfilter.lutrgb" is blacklisted "avfilter.lutyuv" is blacklisted "avfilter.mcdeint" is blacklisted "avfilter.metadata" is blacklisted "avfilter.negate" is blacklisted "avfilter.nlmeans" is blacklisted "avfilter.nnedi" is blacklisted "avfilter.owdenoise" is blacklisted "avfilter.pad" is blacklisted "avfilter.perspective" is blacklisted "avfilter.phase" is blacklisted "avfilter.pixscope" is blacklisted "avfilter.pp" is blacklisted "avfilter.pp7" is blacklisted "avfilter.prewitt" is blacklisted "avfilter.realtime" is blacklisted "avfilter.removegrain" is blacklisted "avfilter.removelogo" is blacklisted "avfilter.roberts" is blacklisted "avfilter.rotate" is blacklisted "avfilter.scale_vaapi" is blacklisted "avfilter.showinfo" is blacklisted "avfilter.shuffleframes" is blacklisted "avfilter.sidedata" is blacklisted "avfilter.signalstats" is blacklisted "avfilter.sobel" is blacklisted "avfilter.stereo3d" is blacklisted "avfilter.super2xsai" is blacklisted "avfilter.swapuv" is blacklisted "avfilter.tblend" is blacklisted "avfilter.tlut2" is blacklisted "avfilter.tonemap" is blacklisted "avfilter.transpose" is blacklisted "avfilter.vectorscope" is blacklisted "avfilter.vflip" is blacklisted "avfilter.vignette" is blacklisted "avfilter.vmafmotion" is blacklisted "avfilter.w3fdif" is blacklisted "avfilter.xbr" is blacklisted "avfilter.yadif" is blacklisted "avfilter.zmq" is blacklisted "avfilter.zoompan" is blacklisted WARNING : Fails to parse "swresample" "gtkrescale" is blacklisted WARNING : Fails to parse "glsl.manager" WARNING : Fails to parse "movit.convert" WARNING : Fails to parse "movit.crop" WARNING : Fails to parse "movit.resample" WARNING : Fails to parse "movit.resize"
[Bug 1975384] [NEW] openshot has started crashing
Public bug reported:
Xubuntu 20.04.4
As of about a week ago, many programs have stopped working. I believe
there was a buggy update that is responsible, although I cannot pinpoint
it specifically.
Clutter-gtk seems to have been changed (eliminated ??) which has
affected many programs. See my report here:
https://bugs.launchpad.net/ubuntu/+bug/1974254
Today I tried to start Openshot, which I have used withing the past two
weeks, and I get the following results. This is a qt app, so it must be
related to something else.
139-> openshot
Copying icon thumbnails to cache
ICONFILE = /u/jeff/.cache/thumbnails/normal/e67402f44e90fe458664fda40767654d.png
Loaded modules from: /tmp/.mount_tySedB/usr/bin
INFO app:
INFO app: Sat May 21 10:57:17 2022
INFO app: Starting new session
INFO app:
INFO app: OpenShot (version 2.6.1)
INFO app:
INFO app: openshot-qt version: 2.6.1
INFO app: libopenshot version: 0.2.7
INFO app: platform: Linux-5.4.0-110-generic-x86_64-with-Ubuntu-20.04-focal
INFO app: processor: x86_64
INFO app: machine: x86_64
INFO app: python version: 3.6.9
INFO app: qt5 version: 5.9.5
INFO app: pyqt5 version: 5.10.1
INFO app: Frozen version info from build server:
{
"build_name": "OpenShot-v2.6.1-release-candidate-8238-59878784-d588dbd6",
"date": "2021-09-04 23:49",
"libopenshot": {
"CI_COMMIT_REF_NAME": "release-20210904",
"CI_COMMIT_SHA": "59878784732fa399c47ac5d282bfc9dfe470d0dc",
"CI_JOB_ID": "27417",
"CI_PIPELINE_ID": "8237",
"CI_PROJECT_NAME": "libopenshot",
"SO": "21",
"VERSION": "0.2.7"
},
"libopenshot-audio": {
"CI_COMMIT_REF_NAME": "release-20210904",
"CI_COMMIT_SHA": "d588dbd6057f71c987dc6d8448322aa6b6e86f1a",
"CI_JOB_ID": "27412",
"CI_PIPELINE_ID": "8236",
"CI_PROJECT_NAME": "libopenshot-audio",
"SO": "8",
"VERSION": "0.2.2"
},
"openshot-qt": {
"CI_COMMIT_REF_NAME": "release-20210904",
"CI_COMMIT_SHA": "11f8e5050bd95c7731beccda28a01fbb481fcf7d",
"CI_JOB_ID": "27422",
"CI_PIPELINE_ID": "8238",
"CI_PROJECT_NAME": "openshot-qt",
"SO": null,
"VERSION": "2.6.1"
}
}
INFO project_data: Setting default profile to HDV 720 24p
INFO language: Qt Detected Languages: ['en-US']
INFO language: LANG Environment Variable: C.UTF-8
INFO language: LOCALE Environment Variable:
INFO language: OpenShot Preference Language: Default
INFO logger_libopenshot: Connecting to libopenshot with debug port: 5556
INFO app: Setting font to /tmp/.mount_tySedB/usr/bin/images/fonts/Ubuntu-R.ttf
INFO app: Setting custom dark theme
INFO ui_util: Initializing UI for MainWindow
WebEngineContext used before QtWebEngine::initialize() or OpenGL context
creation failed.
Installed Qt WebEngine locales directory not found at location
/tmp/.mount_tySedB/usr/bin/translations/qtwebengine_locales. Trying application
directory...
Qt WebEngine locales directory not found at location
/tmp/.mount_tySedB/usr/bin/qtwebengine_locales. Trying fallback directory...
Translations MAY NOT not be correct.
[0521/105720.864468:WARNING:resource_bundle_qt.cpp(115)]
locale_file_path.empty() for locale
Installed Qt WebEngine locales directory not found at location
/tmp/.mount_tySedB/usr/bin/translations/qtwebengine_locales. Trying application
directory...
Qt WebEngine locales directory not found at location
/tmp/.mount_tySedB/usr/bin/qtwebengine_locales. Trying fallback directory...
Translations MAY NOT not be correct.
Path override failed for key ui::DIR_LOCALES and path
'/u/jeff/.QtWebEngineProcess'
[0521/105722.207297:WARNING:resource_bundle_qt.cpp(115)]
locale_file_path.empty() for locale
[3068154:3068338:0521/105723.119801:ERROR:nss_util.cc(808)] After loading Root
Certs, loaded==false: NSS error code: -8018
INFO thumbnail: Starting thumbnail server listening on port 35129
INFO webengine: WebEngine backend initializing
INFO transition_model: updating transitions model.
INFO version: Found current version: {'openshot_version': '2.6.1',
'trans_rate_unstable': 0.001, 'error_rate_unstable': 0.05, 'trans_rate_stable':
0.01, 'error_rate_stable': 0.16}
INFO effects_model: updating effects model.
INFO emoji_model: updating emoji model.
INFO sentry: Sentry initialized with 0.16 error reporting rate (production)
INFO main_window: InitCacheSettings
INFO main_window: cache-mode: CacheMemory
INFO main_window: cache-limit-mb: 250
INFO main_window: Creating CacheMemory object with 262144000 byte limit
INFO preview_thread: QThread Start Method Invoked
ERROR main_window: Unhandled crash detected:
linux-/lib/x86_64-linux-gnu/libc.so.6 abort 0x12b [0x7fbcf8267859]
Failed to create OpenGL context for format QSurfaceFormat(version 2.0,
[Bug 1974254] Re: Probles with Clutter
I wasn't sure of the package so I left field blank. I went back and added clutter-gtk. Hope that helps. ** Also affects: clutter-gtk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974254 Title: Probles with Clutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1974254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974254] [NEW] Probles with Clutter
Public bug reported: Running Xubuntu 20.04.4 I've started seeing all sorts of programs failing in the last week apparently due to clutter. This includes Geeqie and Cheese, and possibly Zoom, although I haven't tracked down the problem there. For example, when I try to start geeqie, I get: Can't initialize clutter-gtk. Start geeqie with the option: --disable-clutter When I try to run cheese I get: (cheese:1207183): Clutter-CRITICAL **: 17:54:24.432: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. ** (cheese:1207183): ERROR **: 17:54:24.432: cheese-application.vala:89: Unable to initialize libcheese-gtk Trace/BPT trap(coredump) In researching the problem I ran across this article: https://blogs.gnome.org/clutter/ Now, I have no idea what clutter is/does, but it seems to now be retired. Was the package removal back-ported to earlier releases of Ubuntu? The gir1.2-gtkclutter-1.0, gir1-clutter-1.0 and gstreamer1.0-clutter-3.0 packages are still installed. Any guidelines here? Thanks. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974254 Title: Probles with Clutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1974254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER
Just to make sure the note is here, my home directory is not in /home at all, but located under /u which is a mount point for an external volume on another disk. I experienced the same problem trying to run a snap. Whatever the solution, it should be generalized to any $HOME location. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776800 Title: Unable to start snap applications if user's home directory is not /home/$USER To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918375] Re: Obscure Window Manager Problem [Enhancement]
Not getting much attention here! :-) Here is some additional information that might be useful. I was having problems with new windows being created and hidden underneath existing windows. In a forum discussion it was suggested to turn off (uncheck) the "Activate focus stealing prevention" on the "Window Manager Tweaks->Focus" tab. This indeed was the problem and once unchecked, new windows were consistently created on the top of the stack. However, this does not address the problem of moving a window that is lower or at the bottom of the window stack to another workspace using keyboard shortcuts. The moving window may still disappear beneath other windows higher in the stack. I have "Raise window when clicking inside application window" set so any attempt to drag a window with the mouse forces it to the top of the stack. My suggestion is that if the user has this option set, that it then also imply that any window movement initiated by a keyboard shortcut also causes the window to be raised so that it will float above all other windows as the virtual desktops (workspaces) change. Unchecking this option would leave the keyboard shortcut action as is. Of course, it would be clearer for everyone involved if this raise-on- window-movement option was given it's own option in the Window Manager or the Window Manager Tweaks menu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918375 Title: Obscure Window Manager Problem [Enhancement] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1918375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859526] Re: xfwm4 crashing after Xubuntu 19.10 upgrade
Yes, after 18.04, it was no longer possible to run two independent desktop sessions, even if you have a single GPU supporting multiple screens. It boggles my mind why this incredibly useful capability was allowed to just die. You can still gang the two screens together with the panel running on one screen and the window manager running across both, but you cannot control them independently; i.e., if you switch desktops both screens change rather than just the one you would like. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859526 Title: xfwm4 crashing after Xubuntu 19.10 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1859526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Regarding my previous comment, disregard the issue about Windows 10 having problems accessing the Samba shares. This turned out to be a strange password problem with samba. Resetting the user's password to the same value that it already was immediately cleared the issue and all windows machines could once again see the shares. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Just to add another voice to the crowd, I'm on Xubuntu 20.04 and I just
ran across this problem myself.
I am using the Nemo file browser, but the same thing occurs with
Nautilus and Thunar. I didn't notice the problem for a long while
because I had three legacy Windows machines on the network (all running
Windows 10 at this point) and had made file browser bookmarks to the
important shares long ago. These bookmarks have continued to work to
this day without issue. I got a new Windows 10 machine a few weeks ago
and was having the problem everyone reports of not being able to connect
("Failed to retrieve share list from server") on the new machine, even
though all the existing bookmarks were still functioning file. All of
the Windows 10 machines were able to see one another without problem.
Then I ran across this thread and tried Bloodyiron's suggestion of
killing the gvfsd-smb-browse process. Immediately I was able to connect
to the new machine using Nemo. I quickly created some needed bookmarks
to the important shares and now I can communicate using the file browser
and expect the new bookmarks to be as reliable as the others. So I
would suggest this bookmark method to others as a workaround.
This supports Craig W's comment about the difference between discovery
and browsing. When I run "smbclient -L // -U ", it
reports all of the shares on the target, whether Windows or Linux, with
the closing message: "SMB1 disabled -- no workgroup available" as
expected.
Unfortunately, this is only a one-way solution. All of the legacy
Windows 10 machines can see and access the Samba shares on the Xubuntu
box, but I haven't yet figured out a way to get the new Windows machine
to access these same shares, with or without gvfsd-smb-browse running.
Every connection attempt is rejected and I haven't found useful messages
in the logs. If I figure out a solution, I'll post here, and I'm open
to suggestions.
I agree with the general sentiment that for a service as important as
this, there isn't any real excuse for this thing dragging out for two
years as it has.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918375] [NEW] Obscure Window Manager Problem [Enhancement]
Public bug reported:
Xubuntu 20.04
xfwm4 4.14.1-0ubuntu1
This is a problem that only occurs under very specific conditions.
However, I think it is problematic enough to deserve consideration for
an enhancement.
My setup includes multiple (8) virtual desktops. I use
Meta-{L,R}ArrowKey to move between desktops and Shift-Meta-{L,R}ArrowKey
to move a specific window across and to different desktops.
My Window Manager settings include:
- Focus Follows Mouse
- Automatically give focus to newly created windows
- Raise window when clicking inside application window
I do not use Auto raise when window receives focus.
The Problem: I move my mouse over a window on the current screen. It
receives focus, but I do not click on it. I want to move the window
three desktops to the left. I use Shift-Meta-LeftArrow to begin moving
the window. I press it three times and discover that I have a mess!
All sorts of things are on the wrong screens. I finally figured out
that the original window is not "raised" because I didn't click on it.
Therefore, as it moved to the first desktop to the left, it got placed
beneath another window there and was completely hidden. The "higher"
window then gets picked up and is moved a screen to the left. It's
possible that the same thing happens (some of my windows are maximized
and fill the entire screen) and the second window gets dropped and the
third window now goes for a ride. If you are not paying very close
attention, this is all extremely confusing.
As I said, this happens because of my particular settings. I don't like
auto raise on focus because it causes a lot of visual jumping on the
screen when you move the mouse around. I did try it out with a long
delay, but the problem described above can still occur.
I would suggest a reasonably simple fix which is whenever a window is
being moved, immediately raise it so that it floats above the other
windows and never gets lost under another window. I assume that raising
a window makes it "higher" then all windows on every desktop, not just
the current one. Thoughts?
** Affects: xfwm4 (Ubuntu)
Importance: Undecided
Status: New
** Tags: focus raise xfwm4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918375
Title:
Obscure Window Manager Problem [Enhancement]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1918375/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918017] Re: ksh93 problems
I did manually install ksh93u and all is back to normal on my machine. However, the 2020 package still gets reported in synaptic, hiding all mention of ksh93. Even under the "Installed (manual)" section, ksh is listed, but still reported as version 2020. There is no recognition of 93u being in the local package DB, even though it is there! So I agree that what Brian is suggesting would be a good thing to get these repositories to 1) distinguish between 93u and 2020, and 2) get 93u listed as the default package, to avoid a lot of confusion. Since it was already replaced shortly after the 20.04 release, this seems like a well tested option that can be adopted without causing regression problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918017 Title: ksh93 problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ksh/+bug/1918017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895246] Re: Plugin calls the incorrect API
Maintainer: please update the 20.04 focal repository with a working package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895246 Title: Plugin calls the incorrect API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-weather-plugin/+bug/1895246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918017] Re: ksh93 problems
** Package changed: ubuntu => ksh (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918017 Title: ksh93 problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ksh/+bug/1918017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918017] [NEW] ksh93 problems
Public bug reported: Running Xubuntu 20.04.02 I've been running ksh93 for 40 years now. Somewhere in the recent past, ksh started performing in strange ways. In particular, it stopped adding commands with faulty syntax to the command history list, rendering them unavailable for recall and editing. Upon further investigation, I discovered that ksh93 had been silently replaced by ksh2020, which is apparently (according to other reports)a buggy and unsupported version of ksh that AT recently washed their hands of. If you look at synaptic, the ksh93 version is not even listed -- only ksh2020. See this image: http://smallthoughts.com/photos/misc/ksh_01.jpg ksh93 is still available in the focal repository and I was able to reinstall it with: apt install ksh93 but it remains unlisted in synaptic. First, ksh2020 is buggy and should not be used -- and certainly not as the primary ksh installation. Second, the distro repository needs to be updated to list the ksh93 package available and made the default. This silent replacement of ksh has caused me many hours of problems! ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918017 Title: ksh93 problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1918017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475620] Re: grub-common does not unset "recordfail" on hibernate when using systemd
I have opened a merge request[1] with the Debian package that addresses this issue. Hope this can be fixed soon. Also, I wanted to note that this isn't an issue with the upstream project since the recordfail functionality is specific to the Debian package[2]. [1]: https://salsa.debian.org/grub-team/grub/-/merge_requests/22 [2]: https://salsa.debian.org/grub-team/grub/-/commit/a2dac38edcc6236bfdbefad4e9654b498843504c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475620 Title: grub-common does not unset "recordfail" on hibernate when using systemd To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1475620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901446] Re: Add gir1.2-tepl-5 package depedency
** Bug watch added: Debian Bug tracker #973312 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973312 ** Also affects: gedit (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973312 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901446 Title: Add gir1.2-tepl-5 package depedency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1901446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901446] Re: Add gir1.2-tepl-5 package depedency
I would argue that this is more a bug than a wishlist item. Functionality is being moved from gedit into tepl (a "Text editor product line" library). For instance, gedit_utils_str_middle_truncate() was deprecated in gedit 3.36 and removed in 3.38[1], replaced with tepl_utils_str_middle_truncate(). For my plugin Control Your Tabs, I had to inline the function[2] because I couldn't count on users (on Debian and Debian-derived OSes) having gir1.2-tepl-5 installed so that I could call tepl_utils_str_middle_truncate(). (Contrast this with the Fedora tepl rpm, which has the GObject introspection binding included in the same package[3] and so does not have this problem.) Should I file an issue upstream (Debian)? Would submitting a patch help? [1]: https://gitlab.gnome.org/GNOME/gedit/-/commit/b21585d0f3ff2081626f6ffb7e1dc1b7a52e [2]: https://github.com/jefferyto/gedit-control-your-tabs/commit/644c2b9d9a61ffd1d8f9aba44866b301ba47bf39 [3]: https://src.fedoraproject.org/rpms/tepl/blob/49ace7de0be692b500d7b2be23224197f96ae296/f/tepl.spec#_60 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901446 Title: Add gir1.2-tepl-5 package depedency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1901446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858152] Re: fstrim.service no longer trims /home partition
groovy has been released with 2.36 so I will mark this issue as fixed. ** Changed in: util-linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: util-linux-ng Importance: Unknown => Undecided ** Changed in: util-linux-ng Status: Unknown => New ** Changed in: util-linux-ng Remote watch: github.com/karelzak/util-linux/issues #824 => None ** Changed in: util-linux-ng Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858152 Title: fstrim.service no longer trims /home partition To manage notifications about this bug go to: https://bugs.launchpad.net/util-linux-ng/+bug/1858152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901446] [NEW] Add gir1.2-tepl-5 package depedency
Public bug reported: (This is most likely a bug/request for Debian, but since I use Ubuntu I thought I would report it here first.) gedit in groovy depends on libtepl-5-0. It would be great if the package also depended on gir1.2-tepl-5 so that gedit plugins written in Python can call functions from tepl. ** Affects: gedit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901446 Title: Add gir1.2-tepl-5 package depedency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1901446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899991] [NEW] indicator-appmenu causing some application menubars to not display
Public bug reported: Xubuntu 20.04 (Ubuntu 20.04.1 LTS) indicator-appmenu 15.02.0+16.10 20160927-0ubuntu5 From std package repository After upgrading to Xubuntu 20-04, I found that the menubar (File, Edit, etc.) was not displaying in LibreOffice and Clementine. Most apps, including xfce4-terminal, GIMP, Firefox, etc., were not affected. With some hints from the web, I uninstalled the indicator-appmenu package, rebooted, and the missing menubars were restored. There seems to be a new problem triggered by 20.04. I see no ill effects so far running Xfce4. Does this package have any function in this environment, or is it specific only to Gnome? ** Affects: indicator-appmenu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/181 Title: indicator-appmenu causing some application menubars to not display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898891] [NEW] anacron cron.weekly error: AttributeError: module 'platform' has no attribute 'linux_distribution'
Public bug reported:
Ever since upgrading to Xubuntu 20.04, anacron throws the following error
weekly. This seems to be a common problem reported on the web regarding python
3.8. Apparently some file or library is outdated, but I have not seen this
error reported in relation to anacron.
--
Subject: Anacron job 'cron.weekly' on .com
/etc/cron.weekly/apt-xapian-index:
ERROR:root:DebFileApplication import
Traceback (most recent call last):
File "/usr/share/software-center/softwarecenter/db/__init__.py", line 6, in
from .debfile import DebFileApplication, DebFileOpenError
File "/usr/share/software-center/softwarecenter/db/debfile.py", line 25, in
from softwarecenter.db.application import Application, AppDetails
File "/usr/share/software-center/softwarecenter/db/application.py", line 28,
in
import softwarecenter.distro
File "/usr/share/software-center/softwarecenter/distro/__init__.py", line 201,
in
distro_instance = _get_distro()
File "/usr/share/software-center/softwarecenter/distro/__init__.py", line 168,
in _get_distro
distro_info = platform.linux_distribution()
AttributeError: module 'platform' has no attribute 'linux_distribution'
Traceback (most recent call last):
File "/usr/sbin/update-apt-xapian-index", line 104, in
if not indexer.setupIndexing(force=opts.force, system=opts.pkgfile is None):
File "/usr/lib/python3/dist-packages/axi/indexer.py", line 473, in
setupIndexing
self.plugins = Plugins(progress=self.progress, system=system)
File "/usr/lib/python3/dist-packages/axi/indexer.py", line 98, in __init__
addon = Addon(fullname, **kw)
File "/usr/lib/python3/dist-packages/axi/indexer.py", line 53, in __init__
self.module = imp.load_source("axi.plugin_" + self.name, fname)
File "/usr/lib/python3.8/imp.py", line 171, in load_source
module = _load(spec)
File "", line 702, in _load
File "", line 671, in _load_unlocked
File "", line 783, in exec_module
File "", line 219, in _call_with_frames_removed
File "/usr/share/apt-xapian-index/plugins/software_center.py", line 13, in
from softwarecenter.db.update import (
File "/usr/share/software-center/softwarecenter/db/update.py", line 33, in
from softwarecenter.backend.scagent import SoftwareCenterAgent
File "/usr/share/software-center/softwarecenter/backend/scagent.py", line 30,
in
from softwarecenter.distro import get_distro, get_current_arch
File "/usr/share/software-center/softwarecenter/distro/__init__.py", line 201,
in
distro_instance = _get_distro()
File "/usr/share/software-center/softwarecenter/distro/__init__.py", line 168,
in _get_distro
distro_info = platform.linux_distribution()
AttributeError: module 'platform' has no attribute 'linux_distribution'
run-parts: /etc/cron.weekly/apt-xapian-index exited with return code 1
** Affects: anacron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898891
Title:
anacron cron.weekly error: AttributeError: module 'platform' has no
attribute 'linux_distribution'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1898891/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509699] Re: The presence of pinentry-qt4 breaks gnupg-agent
Adding keep-display to ~/.gnupg/gpg-agent.conf works for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509699 Title: The presence of pinentry-qt4 breaks gnupg-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1509699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858152] Re: fstrim.service no longer trims /home partition
At this moment, this issue is still present in focal. It would be nice if this can be fixed for an LTS release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858152 Title: fstrim.service no longer trims /home partition To manage notifications about this bug go to: https://bugs.launchpad.net/util-linux-ng/+bug/1858152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871176] Re: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
I got this error after a few steps: * After upgrading from eoan to focal and rebooting, I was dropped into the initramfs shell. Exiting from the shell, I see the error message "/dev/mapper/ubuntu--vg-root does not exist". * After some searching online, I reboot using my previous kernel and reach the desktop. * I open Synaptic and see that lvm2 was removed. When I try to install it, I get the error in this issue. After some more searching online, I see https://askubuntu.com/questions/1049727/every-time-i-install-or- remove-a-package-i-get-lvm2-error/1085420 and try the suggested answer (purge lvm2 before reinstalling) - this worked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871176 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
The scaling issue is affecting me as well: Ubuntu 20.04 LTS AORUS GeForce RTX™ 2080 Ti XTREME 2X Acer Predator XB281HK 4K Monitor - Displayport Connected nvidia-driver-440 Installed alongside Windows 10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861453] [NEW] The chromium-browser snap package fails to run
Public bug reported: Xubuntu 19.10 chromium-browser 79.0.3945.79-0ubuntu0.19.10.2 Transitional package - chromium-browser -> chromium snap Chromium worked fine before the upgrade to 19.10. There has been a transition to snap packaging. My first attempt to launch the browser results in: % chromium-browser 2020/01/30 11:12:47.911841 cmd_run.go:529: WARNING: XAUTHORITY environment value is not a clean path: "/x/u/jeff/.Xauthority" cannot perform operation: mount --rbind /home /tmp/snap.rootfs_MDsNgD//home: Permission denied % dmesg | grep DENIED (just showing one typical message) [827635.380132] audit: type=1400 audit(1580411567.940:87): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/snap/core/8268/usr/lib/snapd/snap-confine" name="/tmp/snap.rootfs_MDsNgD/home/" pid=2968 comm="snap-confine" srcname="/x/u/" flags="rw, rbind" The home directory is: /u/jeff The home directory is actually resides on an external drive mounted on /x with /u being a symlink to /x/u % cd / % ls -l home u lrwxrwxrwx 1 root root 1 Jan 2 2015 home -> u lrwxrwxrwx 1 root root 3 Nov 30 2017 u -> x/u %echo $XAUTHORITY /u/jeff/.Xauthority Applications should not care about these sorts of mounts and linkages, but they now appear to be very sensitive to them. What needs to be done to make this work? BTW, I think this move to SNAP is a disaster and completely the wrong way to go. Let's please stick with a single .deb packaging strategy which has proven itself. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: 19.10 chromium snap xubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861453 Title: The chromium-browser snap package fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1861453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860936] [NEW] No online ksh (or csh) manual page
Public bug reported: Although ksh(1) and csh(1) are supported packages, there does not appear to be a manual page for either, under any release, at http://manpages.ubuntu.com/ These should be added. Accessing from Xubuntu 19.10. ** Affects: ubuntu-manpage-repository Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860936 Title: No online ksh (or csh) manual page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manpage-repository/+bug/1860936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858152] Re: fstrim.service no longer trims /home partition
Thanks Matt. Looks like the fix will be in the next upstream release (2.35). ** Also affects: util-linux-ng via https://github.com/karelzak/util-linux/issues/824 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858152 Title: fstrim.service no longer trims /home partition To manage notifications about this bug go to: https://bugs.launchpad.net/util-linux-ng/+bug/1858152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859526] Re: xfwm4 crashing after Xubuntu 19.10 upgrade
Following up: The xfwm4 crashing problem has to do with defining more than one independent screen in the /etc/X11/xorg.conf file. This is a problem observed by at least one other person. By commenting out the second screen in the ServerLayout section, it was possible to get the system running using the Nvidia drivers. Apparently this bug was also causing audio output to fail for unknown reasons. After the graphics problem was rectified, proper sound operation was once again also restored. I hope this information helps others experiencing this problem. Follow this issue at: https://bugzilla.xfce.org/show_bug.cgi?id=15852 ** Bug watch added: Xfce Bugzilla #15852 https://bugzilla.xfce.org/show_bug.cgi?id=15852 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859526 Title: xfwm4 crashing after Xubuntu 19.10 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1859526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859526] [NEW] xfwm4 crashing after Xubuntu 19.10 upgrade
Public bug reported: After recovering from a failed upgrade from Xubuntu 19.04 to 19.10, I'm left with a system where the xfwm4 window manager is constantly crashing. I get a desktop on my primary screen :0.0 but there is neither a xfce4-panel nor a window manager. With great difficulty I can start apps, but without the window manager, there is no way to move, resize or close them. Overlapping or hidden windows remain as such. You cannot use right-click or pull-down menus in most apps. Every attempt to start xfwm4 results in a crash with a crash file in /var/crash. This message in kern.log: Jan 12 20:22:38 dymaxion kernel: [ 54.589712] traps: xfwm4[5044] trap int3 ip:7fc4d1afb8e5 sp:7fff265927e0 error:0 in libglib-2.0.so.0.6200.1[7fc4d1ac+83000] indicates that the problem is an interaction with libglib-2.0.so.0.6200.1. Both xfwm4 and the libglib package that provides the above library have been reinstalled. Any suggestions would be greatly appreciated as I'm pretty much dead in the water at the moment. PS: This bug was also reported to the XFCE group here: https://bugzilla.xfce.org/show_bug.cgi?id=16374 ** Affects: xfwm4 (Ubuntu) Importance: Undecided Status: New ** Tags: 19.10 crash upgrade xfwm4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859526 Title: xfwm4 crashing after Xubuntu 19.10 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1859526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858152] [NEW] fstrim.service no longer trims /home partition
Public bug reported: When I was running disco, fstrim.service would trim all of my partitions: Oct 21 00:00:18 computer systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Oct 21 00:00:37 computer fstrim[9588]: /home: 25 GiB (26797150208 bytes) trimmed on /dev/mapper/ubuntu--vg-home Oct 21 00:00:37 computer fstrim[9588]: /boot: 805.4 MiB (844546048 bytes) trimmed on /dev/sda5 Oct 21 00:00:37 computer fstrim[9588]: /: 5.5 GiB (5929816064 bytes) trimmed on /dev/mapper/ubuntu--vg-root Oct 21 00:00:37 computer systemd[1]: fstrim.service: Succeeded. Oct 21 00:00:37 computer systemd[1]: Started Discard unused blocks on filesystems from /etc/fstab. After upgrading to eoan, my /home partition is no longer trimmed: Oct 28 00:00:21 computer systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Oct 28 00:00:32 computer fstrim[24667]: /boot: 781.1 MiB (819011584 bytes) trimmed on /dev/sda5 Oct 28 00:00:32 computer fstrim[24667]: /: 7.2 GiB (7696994304 bytes) trimmed on /dev/mapper/ubuntu--vg-root Oct 28 00:00:32 computer systemd[1]: fstrim.service: Succeeded. Oct 28 00:00:32 computer systemd[1]: Started Discard unused blocks on filesystems from /etc/fstab. Checking the unit file (/lib/systemd/system/fstrim.service), I noticed there is a "ProtectHome=yes" option. Removing this option caused my /home partition to be trimmed once again. I believe the "ProtectSystem=strict" option may also cause partitions in non-standard partition schemes to be skipped by fstrim.service (although I have not tested this). ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858152 Title: fstrim.service no longer trims /home partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846510] Re: xfpanel-switch fails to save panel settings
Here it is. ** Attachment added: "xfce4-panel.xml" https://bugs.launchpad.net/ubuntu/+source/xfpanel-switch/+bug/1846510/+attachment/5294139/+files/xfce4-panel.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846510 Title: xfpanel-switch fails to save panel settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfpanel-switch/+bug/1846510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846510] [NEW] xfpanel-switch fails to save panel settings
Public bug reported:
I originally reported this under bugid 1765565, but was asked to open
this report as a new bug.
I'm on Xubuntu 19.04, fully patched with xfpanel-switch version
1.0.7-ubuntu2 and I'm having the same or similar problem as noted by the
original reporter (bugid 1765565). When I start xfpanel-switch manually,
here are the errors reported upon startup, when the first save
configuration is pressed, and finally when Save Configuration is
selected from the pop-up menu. This may have existed in 18.10 (I don't
know) but I upgraded to 19.04 recently. The last saved config is labeled
Xubuntu Disco from 08-21-19. I cannot remember if I made this manually
or if it was done automatically as part of the upgrade.
234-> xfpanel-switch
/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py:132:
DeprecationWarning: Gtk.Widget.override_background_color is deprecated
self.xfce_header.override_background_color(0, base_color[1])
/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py:134:
DeprecationWarning: Gtk.Widget.override_color is deprecated
self.xfce_header.override_color(0, fg_color[1])
[press save configuration button]
/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py:309:
PyGTKDeprecationWarning: The keyword(s) "message_format" have been deprecated
in favor of "text" respectively. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
_("Save Configuration"), Gtk.ResponseType.ACCEPT))
/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py:309:
PyGTKDeprecationWarning: The "buttons" argument must be a Gtk.ButtonsType enum
value. Please use the "add_buttons" method for adding buttons. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
_("Save Configuration"), Gtk.ResponseType.ACCEPT))
[press Save Configuration to make backup from pop-up menu]
Traceback (most recent call last):
File "/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py", line 221,
in on_save_clicked
self.save_configuration(name)
File "/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py", line 209,
in save_configuration
PanelConfig.from_xfconf(self.xfconf).to_file(filename)
File "/usr/share/xfpanel-switch/xfpanel-switch/panelconfig.py", line 65, in
from_xfconf
pc.find_desktops()
File "/usr/share/xfpanel-switch/xfpanel-switch/panelconfig.py", line 148, in
find_desktops
self.remove_keys(rem_keys)
File "/usr/share/xfpanel-switch/xfpanel-switch/panelconfig.py", line 155, in
remove_keys
del self.properties[param]
KeyError: '/plugins/plugin-48'
Nothing happens and nothing is saved. An attempt to export the
configuration fails as follows:
[press the export button]
/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py:99:
PyGTKDeprecationWarning: Using positional arguments with the GObject
constructor has been deprecated. Please specify keyword(s) for "title, parent,
action, buttons" or use a class specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
button, Gtk.ResponseType.ACCEPT))
/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py:99:
PyGTKDeprecationWarning: The "buttons" argument must be a Gtk.ButtonsType enum
value. Please use the "add_buttons" method for adding buttons. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
button, Gtk.ResponseType.ACCEPT))
[Export configuration as ... pop-up appears. Regardless of where you
navigate, pressing Save fails]
Traceback (most recent call last):
File "/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py", line 234,
in on_export_clicked
self.save_configuration(filename, False)
File "/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py", line 209,
in save_configuration
PanelConfig.from_xfconf(self.xfconf).to_file(filename)
File "/usr/share/xfpanel-switch/xfpanel-switch/panelconfig.py", line 65, in
from_xfconf
pc.find_desktops()
File "/usr/share/xfpanel-switch/xfpanel-switch/panelconfig.py", line 148, in
find_desktops
self.remove_keys(rem_keys)
File "/usr/share/xfpanel-switch/xfpanel-switch/panelconfig.py", line 155, in
remove_keys
del self.properties[param]
KeyError: '/plugins/plugin-48'
[Nothing is written]
I have not deleted panels, but I have struggled with Xfce4 on my dual-
headed system since support for independent parallel desktops running
(non-Xinerama mode) on each screen in Xubuntu 18.10 was broken. This may
be due to moving to gtk3, but it is a serious degradation of service
since xfdesktop and xfce4-panel no longer honor the display option.
(Note: xfwm4 still works on two independent displays!) I mention this
first and foremost because I want to see this fixed, and second because
there were two different panels defined on this system at one point --
one for each display -- and that may have some bearing on what may be
causing this problem. I'm running Xubuntu on a desktop Intel machine
with dual 4K monitors using a Nvidia Quadro K4000 GPU.
If you need further
[Bug 1360071] Re: Scrollbar has non-standard operation
Just checking back. It is now 09-30-19, I'm on Xubuntu 19.04, and this has not yet been addressed in Synaptic 0.84.5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360071 Title: Scrollbar has non-standard operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1360071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765565] Re: xfpanel-switch is failing to save panel settings
I'm on Xubuntu 19.04, fully patched with xfpanel-switch version
1.0.7-ubuntu2 and I'm having the same or similar problem as noted by the
original reporter. When I start xfpanel-switch manually, here are the
errors reported upon startup, when the first save configuration is
pressed, and finally when Save Configuration is selected from the pop-up
menu. This may have existed in 18.10 (I don't know) but I upgraded to
19.04 recently. The last saved config is labeled Xubuntu Disco from
08-21-19. I cannot remember if I made this manually or if it was done
automatically as part of the upgrade.
234-> xfpanel-switch
/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py:132:
DeprecationWarning: Gtk.Widget.override_background_color is deprecated
self.xfce_header.override_background_color(0, base_color[1])
/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py:134:
DeprecationWarning: Gtk.Widget.override_color is deprecated
self.xfce_header.override_color(0, fg_color[1])
[press save configuration button]
/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py:309:
PyGTKDeprecationWarning: The keyword(s) "message_format" have been deprecated
in favor of "text" respectively. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
_("Save Configuration"), Gtk.ResponseType.ACCEPT))
/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py:309:
PyGTKDeprecationWarning: The "buttons" argument must be a Gtk.ButtonsType enum
value. Please use the "add_buttons" method for adding buttons. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
_("Save Configuration"), Gtk.ResponseType.ACCEPT))
[press Save Configuration to make backup from pop-up menu]
Traceback (most recent call last):
File "/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py", line 221,
in on_save_clicked
self.save_configuration(name)
File "/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py", line 209,
in save_configuration
PanelConfig.from_xfconf(self.xfconf).to_file(filename)
File "/usr/share/xfpanel-switch/xfpanel-switch/panelconfig.py", line 65, in
from_xfconf
pc.find_desktops()
File "/usr/share/xfpanel-switch/xfpanel-switch/panelconfig.py", line 148, in
find_desktops
self.remove_keys(rem_keys)
File "/usr/share/xfpanel-switch/xfpanel-switch/panelconfig.py", line 155, in
remove_keys
del self.properties[param]
KeyError: '/plugins/plugin-48'
Nothing happens and nothing is saved. An attempt to export the configuration
fails as follows:
[press the export button]
/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py:99:
PyGTKDeprecationWarning: Using positional arguments with the GObject
constructor has been deprecated. Please specify keyword(s) for "title, parent,
action, buttons" or use a class specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
button, Gtk.ResponseType.ACCEPT))
/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py:99:
PyGTKDeprecationWarning: The "buttons" argument must be a Gtk.ButtonsType enum
value. Please use the "add_buttons" method for adding buttons. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
button, Gtk.ResponseType.ACCEPT))
[Export configuration as ... pop-up appears. Regardless of where you
navigate, pressing Save fails]
Traceback (most recent call last):
File "/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py", line 234,
in on_export_clicked
self.save_configuration(filename, False)
File "/usr/share/xfpanel-switch/xfpanel-switch/xfpanel-switch.py", line 209,
in save_configuration
PanelConfig.from_xfconf(self.xfconf).to_file(filename)
File "/usr/share/xfpanel-switch/xfpanel-switch/panelconfig.py", line 65, in
from_xfconf
pc.find_desktops()
File "/usr/share/xfpanel-switch/xfpanel-switch/panelconfig.py", line 148, in
find_desktops
self.remove_keys(rem_keys)
File "/usr/share/xfpanel-switch/xfpanel-switch/panelconfig.py", line 155, in
remove_keys
del self.properties[param]
KeyError: '/plugins/plugin-48'
[Nothing is written]
I have not deleted panels, but I have struggled with Xfce4 on my dual-headed
system since support for independent parallel desktops running (non-Xinerama
mode) on each screen in Xubuntu 18.10 was broken. This may be due to moving to
gtk3, but it is a serious degradation of service since xfdesktop and
xfce4-panel no longer honor the display option. (Note: xfwm4 still works on
two independent displays!) I mention this first and foremost because I want to
see this fixed, and second because there were two different panels defined on
this system at one point -- one for each display -- and that may have some
bearing on what may be causing this problem.
If you need further config info from this system, please let be know.
I'm not currently sure where to look for the panel definitions and don't
want to much up my current working panel.
--
You received this bug notification because you
[Bug 1843192] [NEW] Requesting update for xtide package
Public bug reported: Xubuntu 19.04 Xtide 2.13.2 package from the standard package repository There is a newer version of xtide available. The current package is not compiled against livxaw3dxft and consequently does not have support for most Ubuntu fonts. Adding this would be a great improvement. For info, see: https://flaterco.com/xtide/faq.html Q: The text in XTide windows uses uglyfont. ** Affects: xtide (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843192 Title: Requesting update for xtide package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xtide/+bug/1843192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822181] Re: Ubuntu 18.10 broke dual-screen dual-desktop configuration
I am VERY interested in continuing work on this. I'm now running 19.04 and the problem persists. I cannot change the status so please update it. There has been a long running discussion on the Xfce buglist which you can review here: https://bugzilla.xfce.org/show_bug.cgi?id=15116 The problem seems to be that the move to gtk3 is the source of the condition as it has dropped support for multiple monitors. Olivier Fourdan is maintaining xfwm4 and he has apparently done something internally that allows X11-aware applications to be launched on a separate display (:0.1) in addition to the native display (:0.0), but none of the other Xfce components such as the panel, desktop, etc have the ability to run more than one instance on the main display. In this forum discussion: https://forum.xfce.org/viewtopic.php?pid=50336#p50336 member gert pointed to this patch in the gtk3 repository that seems to indicate that multi-screen support has been added back into the toolkit. https://github.com/xfce- mirror/xfwm4/commit/b52c2f5b740434803342c471d4dcb5dd62eb99a1 However, this patched version of gtk has not yet made it into a Ubuntu distribution. Losing multi-headed independent desktop support has been a terrible step backwards for Ubuntu. Please look into this more closely and make sure that the 19.10 release gets the tools required to get this capability restored. I'll provide additional info if necessary. However, as an end0user in this arena, I don't have more insights into the interactions of the display components making up the various desktop environments. On a couple of other forums, I asked whether there was another flavor of Ubuntu that was properly supporting multiple screens. I received zero replies. Multiple independent desktops is critical (as opposed to Xinerama mode) so that material can be displayed statically on one display while changing workspaces on the other screen. ** Bug watch added: Xfce Bugzilla #15116 https://bugzilla.xfce.org/show_bug.cgi?id=15116 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822181 Title: Ubuntu 18.10 broke dual-screen dual-desktop configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1822181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822866] Re: package sendmail-bin 8.15.2-12 failed to install/upgrade: installed sendmail-bin package post-installation script subprocess returned error exit status 2
Just adding another voice to this thread. I had the same problem during the upgrade. The failure for sendmail-bin to properly configure caused the sensible-mta, dovecot-core and inn2 packages to all fail to properly update due to dependency problems. Thanks to Mirko above, who suggested a solution. Stopping the sendmail service and running "apt install -f" allowed the configuration to complete. In case it is any help, here are the relevant log messages: Messages from /var/log/dist-upgrade/main.log: ERROR got an error from dpkg for pkg: 'sendmail-bin': 'installed sendmail-bin package post-installation script subprocess returned error exit status 2' 2019-07-07 22:44:50,515 DEBUG running apport_pkgfailure() sendmail-bin: installed sendmail-bin package post-installation script subprocess returned error exit status 2 2019-07-07 22:44:50,528 ERROR got an error from dpkg for pkg: 'sendmail-bin': 'installed sendmail-bin package post-installation script subprocess returned error exit status 2' 2019-07-07 22:47:47,560 ERROR got an error from dpkg for pkg: 'sendmail': 'dependency problems - leaving unconfigured' 2019-07-07 22:47:47,561 DEBUG running apport_pkgfailure() sendmail: dependency problems - leaving unconfigured 2019-07-07 22:47:47,561 DEBUG dpkg error because of dependency problems, not reporting against sendmail 2019-07-07 22:47:47,561 ERROR got an error from dpkg for pkg: 'sendmail': 'dependency problems - leaving unconfigured' 2019-07-07 22:47:47,758 ERROR got an error from dpkg for pkg: 'sensible-mda': 'dependency problems - leaving unconfigured' 2019-07-07 22:47:47,758 DEBUG running apport_pkgfailure() sensible-mda: dependency problems - leaving unconfigured 2019-07-07 22:47:47,759 DEBUG dpkg error because of dependency problems, not reporting against sensible-mda 2019-07-07 22:47:47,759 ERROR got an error from dpkg for pkg: 'sensible-mda': 'dependency problems - leaving unconfigured' 2019-07-07 22:47:48,269 ERROR got an error from dpkg for pkg: 'inn2': 'dependency problems - leaving unconfigured' 2019-07-07 22:47:48,270 DEBUG running apport_pkgfailure() inn2: dependency problems - leaving unconfigured 2019-07-07 22:47:48,270 DEBUG dpkg error because of dependency problems, not reporting against inn2 2019-07-07 22:47:48,270 ERROR got an error from dpkg for pkg: 'inn2': 'dependency problems - leaving unconfigured' 2019-07-07 22:47:52,116 ERROR got an error from dpkg for pkg: 'dovecot-core': 'triggers looping, abandoned' 2019-07-07 22:47:52,116 DEBUG running apport_pkgfailure() dovecot-core: triggers looping, abandoned 2019-07-07 22:47:52,132 ERROR got an error from dpkg for pkg: 'dovecot-core': 'triggers looping, abandoned' 2019-07-07 22:51:47,341 ERROR Exception during pm.DoInstall() Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-nggm0iiu/DistUpgrade/DistUpgradeView.py", line 220, in run res = pm.do_install(self.writefd) apt_pkg.Error: E:Sub-process /usr/bin/dpkg returned an error code (1) 2019-07-07 22:51:47,369 ERROR SystemError from cache.commit(): installArchives() failed 2019-07-07 22:51:47,370 ERROR found exception: 'E:Sub-process /usr/bin/dpkg returned an error code (1)' 2019-07-07 22:55:43,205 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' 2019-07-07 22:55:43,218 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) Messages from /var/log/dist-upgrade/apt-term.log: Setting up sendmail-bin (8.15.2-12) ... Installing new version of config file /etc/init.d/sendmail ... update-alternatives: warning: forcing reinstallation of alternative /usr/lib/sm.bin/sendmail because link group sendmail-mta is broken Saving old /etc/mail/sendmail.cf as /etc/mail/sendmail.cf.old ... start-stop-daemon: matching only on non-root pidfile /var/run/sendmail/mta/sendmail.pid is insecure dpkg: error processing package sendmail-bin (--configure): installed sendmail-bin package post-installation script subprocess returned error exit status 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822866 Title: package sendmail-bin 8.15.2-12 failed to install/upgrade: installed sendmail-bin package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sendmail/+bug/1822866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825249] Re: fonts garbled in firefox browser -- only on certain pages
No, I haven't done that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825249 Title: fonts garbled in firefox browser -- only on certain pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1825249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822181] Re: Ubuntu 18.10 broke dual-screen dual-desktop configuration
As previously reported, I've tried a number of different Nvidia and the X.Org drivers with no better results. And as previously reported: -- 54-> xrandr Screen 0: minimum 8 x 8, current 1600 x 1200, maximum 16384 x 16384 DVI-I-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 432mm x 324mm 1600x1200 60.00*+ 1280x1024 85.0275.0260.02 1024x768 85.0075.0370.0760.00 800x600 85.0675.0072.1960.3256.25 640x480 85.0175.0072.8159.94 DVI-I-1 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis Note: No DP-3? RandR must be numbering the display ports differently from NVIDIA. The above output is identical to what you get with the command: xrandr -display :0.0 However, you can probe the second screen with the command: xrandr -display :0.1 55-> xrandr -display :0.1 Screen 1: minimum 8 x 8, current 1600 x 1200, maximum 16384 x 16384 DP-3 connected primary 1600x1200+0+0 (normal left inverted right x axis y axis) 432mm x 324mm 1600x1200 60.00*+ 1280x1024 85.0275.0260.02 1024x768 85.0075.0370.0760.00 800x600 85.0675.0072.1960.3256.25 640x480 85.0175.0072.8159.94 -- So, as you can see, RandR DOES know about the second display, but it does not properly integrate it into the system. Since you say that Xfce is built upon RandR, I'd say that that may be the place to start. I don't know what is going on down at this level, but if someone in the developer community thinks this is actually a RandR problem, please change the target package from my guess of xfwm4 to libxrandr2 or whatever you think appropriate. Still, this is a lot of theorizing when someone in the developer group could be testing this out on a dual screen configuration and see what actually happens! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822181 Title: Ubuntu 18.10 broke dual-screen dual-desktop configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1822181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822181] Re: Ubuntu 18.10 broke dual-screen dual-desktop configuration
Steve, I also made an earlier report to Nvidia regarding this. You might consider adding a comment at the following link in order to prod more discussion and involvement there as well. Regards. https://devtalk.nvidia.com/default/topic/1046553/linux/quadro-k4000 -second-monitor-problem-on-xubuntu-18-04/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822181 Title: Ubuntu 18.10 broke dual-screen dual-desktop configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1822181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822181] Re: Ubuntu 18.10 broke dual-screen dual-desktop configuration
Steve, thanks for looking into this with 19.04. I wasn't expecting that it would improve things, but I decided that if I was going to pour more effort into this, U would wait for the next OS release. Yes, the other post may not be directly relevant to our problem, but it's still interesting. I've thought that some underlying change may have been made to disallow a second session manager to run, so this might be a clue as to where to look. I get the same xrandr results as you. % xrandr -q Screen 0: minimum 8 x 8, current 1600 x 1200, maximum 16384 x 16384 DVI-I-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 432mm x 324mm 1600x1200 60.00*+ 1280x1024 85.0275.0260.02 1024x768 85.0075.0370.0760.00 800x600 85.0675.0072.1960.3256.25 640x480 85.0175.0072.8159.94 DVI-I-1 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) % xrandr -display :0.1 Screen 1: minimum 8 x 8, current 1600 x 1200, maximum 16384 x 16384 DP-3 connected primary 1600x1200+0+0 (normal left inverted right x axis y axis) 432mm x 324mm 1600x1200 60.00*+ 1280x1024 85.0275.0260.02 1024x768 85.0075.0370.0760.00 800x600 85.0675.0072.1960.3256.25 640x480 85.0175.0072.8159.94 Now, can we get developers responsible for different parts of the OS related to display recognition and the launching of xfce4 to please coordinate on this problem and track down the source. It definitely happened due to a change from 18.04 to 18.10, so diffs between those two versions is the place to look. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822181 Title: Ubuntu 18.10 broke dual-screen dual-desktop configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1822181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822181] Re: Ubuntu 18.10 broke dual-screen dual-desktop configuration
Thanks Steve. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822181 Title: Ubuntu 18.10 broke dual-screen dual-desktop configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1822181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822181] Re: Ubuntu 18.10 broke dual-screen dual-desktop configuration
Steve, glad to see that there is someone else with this problem, but sorry that you are also experiencing the difficulties. Like Steve, I tried using Xinerama and was able to get the single desktop to span the two monitors, but starting a second desktop, as desired, does not work. This is why I identified the window manager as a possible locus of the problem. If someone thinks it relates to a different package, please make the necessary change. I have upgraded Xubuntu many times up through 18.04 and had no problem. There is definitely something significant that changed in 18.10 that caused this problem. From the outside it is difficult to determine where to point the finger as to what may be the source of the problem. That is why I was hoping that a variety of people working on the core components affecting this could look into it. I tried to provide as much configuration and diagnostics information as I could in order to allow someone with a test setup to add a second monitor and configure it for dual independent desktops and see what results you get. As I said before, this configuration should be part of the standard testing before any release, and well documented. BTW, I've also been (long ago) in discussions with the Nvidia people and they/I don't think it has anything to do with their driver. I tried a number of different Nvidia driver packages as well as the Xorg version, and nothing made any difference. I will upgrade and test with 19.04 when released (what have I got to lose) but this machine is my live work system and I really cannot screw with it too much as a test bed. And like Steve, I'll happily provide any additional info I can, upon request. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822181 Title: Ubuntu 18.10 broke dual-screen dual-desktop configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1822181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825249] [NEW] fonts garbled in firefox browser -- only on certain pages
Public bug reported: Xubuntu 18.10 and earlier releases Firefox browser 66.0.3 and every earlier version of the Quantum releases There has been a font display problem on Firefox add-on pages (and a very few other random sites) ever since the Quantum browser was released. I reported this to the Firefox team well over a year ago here: https://bugzilla.mozilla.org/show_bug.cgi?id=1437338 with periodic follow-up here: https://bugzilla.mozilla.org/show_bug.cgi?id=1446688 You can see a recent example of the problem here: http://smallthoughts.com/photos/misc/firefox_66_01.png Now, while I'm convinced that this is likely a Firefox problem, I cannot get anyone there to reproduce the problem. So on the chance that it's related to some font glitch on the Ubuntu system, I'm reporting it here to see if anyone can reproduce the problem. If you could load a recent version of Firefox and visit this (or any add-on) page: https://addons.mozilla.org/en-US/firefox/addon/autofill- quantum/?src=search and see if you observe what I'm observing, it would be great in helping track down the source of this extremely annoying glitch. BTW, this ONLY happen in Firefox, not in the Chromium or Opera browsers, and it does not happen in Firefox running under Windows 10 in a VM on the same machine. Thanks for any insights as to what might be causing this. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825249 Title: fonts garbled in firefox browser -- only on certain pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1825249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822181] Re: Ubuntu 18.10 broke dual-screen dual-desktop configuration
Is there anyone else in the Xubuntu world running a dual monitor dual desktop configuration? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822181 Title: Ubuntu 18.10 broke dual-screen dual-desktop configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1822181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822181] Re: Ubuntu 18.10 broke dual-screen dual-desktop configuration
Any takers? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822181 Title: Ubuntu 18.10 broke dual-screen dual-desktop configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1822181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822181] Re: Ubuntu 18.10 broke dual-screen dual-desktop configuration
This is an automated message: OK automated message, I'd be happy to list a specific source package if I knew what it might be. I really am not sure what might be responsible here any more than the people in the Xfce group were. If some humans on the team could review this issue and have a suggestion as to where to focus, I would be happy to add one or more packages or let others fill in that info. I'm not sure how the core Ubuntu system is broken down. I'll tag it against xfwm4, but I'm not sure that the problem is more fundamental than at the window manager level. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822181 Title: Ubuntu 18.10 broke dual-screen dual-desktop configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1822181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822181] Re: Ubuntu 18.10 broke dual-screen dual-desktop configuration
Not sure that this is the correct package, but it's a starting point. ** Package changed: ubuntu => xfwm4 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822181 Title: Ubuntu 18.10 broke dual-screen dual-desktop configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1822181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822181] [NEW] Ubuntu 18.10 broke dual-screen dual-desktop configuration
Public bug reported: I'm running Xubuntu. I finally reported this problem to the Xfce group and received this response: "As arandr/xrandr does not detect correctly your 2nd screen, this seems that it is not related directly to Xfce, but a bug in Xubuntu stack. Can you please open a bug on Xubuntu project if the issue is still present for you?" Thus this bug report. I've been running Xubuntu for years with two monitors, each running an independent xfce4 desktop -- i.e., configured without Xinerama. This has worked fine for every upgrade through 18.04. When upgrading to 18.10, something significant changed and the the second monitor (display :0.1) was disabled. After much reading and work, I have only been able to restore some extremely hobbled functionality. I am unable to get a second xfce4-desktop, panel or window manager running on the second screen. I have assembled detailed screenshots and command output at the following link: http://smallthoughts.com/xfce/xfce.html I'm using an NVIDIA Quadro K-4000 graphics card and no hardware changes were made between 18.04 and 18.10. The nvidia-settings tool reports both monitors active (as configured in /etc/X11/xorg.conf) but the xfce4-display-settings and aarandr tools each show only one display (although xrandr can be forced to report on the second display. See full documentation at the above link.) What changed in the latest release, and what needs to be done to get the second monitor running a second desktop once again? I have been struggling with this for many months now and it has severely impacted the use of my system. As a new release of Ubuntu in coming, I would appreciate it if this could be prioritized and addressed as quickly as possible. I will provide additional information upon request. P.S.: There is really no documentation available on running multiple desktops on separate screens when Xinerama is not used to tie the screens together into a single desktop. This is a common configuration and I would like to request that as part of the solution to this problem, the setup steps be documented and this multi-desktop configuration be made a standard part of the development and testing process for each Ubuntu release. 13-> lsb_release -rd Description:Ubuntu 18.10 Release:18.10 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: 18.10 desktop dual-screen xubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822181 Title: Ubuntu 18.10 broke dual-screen dual-desktop configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1822181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814838] Re: xpdf
There is now a 4.01.01 version. I have found that the pre-compiled versions on the XpdfReader.com site do not properly support printing to local printers, but a custom compiled version under Xubuntu 18.10 with system libraries does work. Please check that cups printers are displayed on the print dialog before packaging. Regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814838 Title: xpdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/1814838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814838] [NEW] xpdf
Public bug reported: Ubuntu 18.10 There is a new version 4.00.01 of xpdf and associated tools, available since 08-15-17. The current 3.04 version should be updated in the package archives. http://www.xpdfreader.com/download.html ** Affects: ubuntu Importance: Undecided Status: New ** Tags: xpdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814838 Title: xpdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1814838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786822] Re: Pinta constantly crashes in Ubuntu 18.04 fresh install
Same with me Tom. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786822 Title: Pinta constantly crashes in Ubuntu 18.04 fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/pinta/+bug/1786822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
I had the exact same problem with my Intel NUC5CPYH which uses the Braswell chipset. After reading a lot of other articles I found this worked for me and now I can move my mouse anywhere on the desktop and my whole experience is a lot snappier: 1. Create a new xorg.conf file in your home directory: sudo X :1 -configure 2. Edit the new xorg.conf.new file and modify/uncomment the following lines in the "Device" section: Driver "intel" Option "AccelMethod" "sna" Option "TearFree" "true" Option "DRI" "3" 3. Copy the file to the /usr/share/X11/xorg.conf.d directory and name it 20-intel.conf: sudo cp xorg.conf.new /usr/share/X11/xorg.conf.d/20-intel.conf 4. Either reboot or restart the gdm service. If it doesn't work other posters suggested using "uxa" as the AccelMethod but apparently "sna" is faster. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796614] Re: [nouveau] Ubuntu 18.10 boots to a blank screen with a blinking cursor
I also have this problem. Differences for me: I have a RTX 2080 and installed Nvidia's 410.78 driver manually. Whenever I boot, I too get the black screen with a blinking cursor. I also have the ctrl+alt+F3, login and run startx This brings me to the gnome desktop instead of the traditional Ubuntu desktop. I am not really sure how to fix this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796614 Title: [nouveau] Ubuntu 18.10 boots to a blank screen with a blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1796614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796614] Re: [nouveau] Ubuntu 18.10 boots to a blank screen with a blinking cursor
I also have this problem. Differences for me: I have a RTX 2080 and installed Nvidia's 410.78 driver manually. Whenever I boot, I too get the black screen with a blinking cursor. I also have the ctrl+alt+F3, login and run startx This brings me to the gnome desktop instead of the traditional Ubuntu desktop. I am not really sure how to fix this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796614 Title: [nouveau] Ubuntu 18.10 boots to a blank screen with a blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1796614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796614] Re: [nouveau] Ubuntu 18.10 boots to a blank screen with a blinking cursor
Caveat: Thanks Christopher... I duplicated your solution by editing the /etc/gdm3/custom.conf Everything seems to be working again. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796614 Title: [nouveau] Ubuntu 18.10 boots to a blank screen with a blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1796614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1
@Adrian Limmi: 1. Open the Add-ons Manager in Thunderbird, and go to the Extensions page/tab (if it isn't already open). 2. At the top of the page, click the gear button next to the search box to open a menu, then select "Install Add-on From File". 3. From here you can select the .xpi file and it should install without issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797945 Title: Lightning incompatible with Thunderbird 60.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545778] Re: xul-ext-lightning is only available in English
I've extracted all of the language/locale versions of Lightning 6.2.2.1 from the Thunderbird 60.2.1 Linux (binary) release tarballs, they are available at: https://www.dropbox.com/sh/w84dtrc73e90j3p/AABC5CeNN- ZwoNgq9m1hQUs4a/thunderbird-60.2.1?dl=0=_nav_tracking=1 If you are reluctant to install an extension from some random Internet person (I wouldn't blame you), you can also download the release tarball for your locale from the Thunderbird homepage (https://www.thunderbird.net/), then extract the .xpi file from the thunderbird/distribution/extensions directory (inside the archive). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/545778 Title: xul-ext-lightning is only available in English To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/545778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1
Instead of everyone having to download and extract their own .xpi file, I decided to do it myself and upload all the language/locale versions of the extension to here: https://www.dropbox.com/sh/w84dtrc73e90j3p/AABC5CeNN- ZwoNgq9m1hQUs4a/thunderbird-60.2.1?dl=0=_nav_tracking=1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797945 Title: Lightning incompatible with Thunderbird 60.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1
Recent versions of Thunderbird (at least the version packaged / distributed by Mozilla) has come pre-installed with Lightning; this is why the extension hasn't been updated on addons.mozilla.org. The version of Thunderbird installable from the standard Ubuntu repositories is packaged by Ubuntu. They have chosen to package the extension as a separate package (xul-ext-lightning), so the most "correct" solution to this issue is to install that package. (xul-ext-lightning being English-only appears to be long-standing issue (#545778); if this affects you I suggest contributing to that bug report.) If you would still like to install the .xpi file (perhaps because of the locale issue): 1. Visit the Thunderbird site (https://www.thunderbird.net/) and download the Linux / Linux 64-bit version of Thunderbird, matching your installed version (60.2.1 in this case) and locale. It should be a .tar.bz2 archive. 2. Extract the archive, then inside thunderbird/distribution/extensions there should be one .xpi file. That should be the corresponding version of Lightning (6.2.2.1). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797945 Title: Lightning incompatible with Thunderbird 60.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1
The bug report for "xul-ext-lightning is only available in English" is at https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/545778 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797945 Title: Lightning incompatible with Thunderbird 60.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798034] Re: Package xul-ext-lightning is in English only
Appears to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/545778 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798034 Title: Package xul-ext-lightning is in English only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1798034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798102] Re: Lightning no longer in French after upgrading to 60.2.1
Appears to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/545778 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798102 Title: Lightning no longer in French after upgrading to 60.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1798102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243354] Re: Xfce4-terminal cannot run on more than one X screen at a time
Xubuntu 18.04: I also have two screens running two different Xfce sessions, and like others reporting here, I have had a devil of a time getting this xfce4-terminal program to run on the two monitors by specifying the --display=:0.0 and --display=:0.1 options. I have a script that launches the terminal windows on the appropriate screen using the proper options. This works -- then it stops working. Then I get it working again and then it stops working again. This has been going on for years. A short while ago I had to dive into this yet again and I got things working so that I could open terminals on both screens. This has been good now for the past few weeks. There were no recent upgrades on the system, but I had some sort of smbd(8) fault a short while ago and decided to reboot. When the system came up, I simply could not get xfce4-terminal to start on display :0.1. Even if I selected Terminal Emulator from the built-in Applications menu on the second screen, it would still only start on display :0.0. After another reboot and then screwing around for two more hours, I went looking for a place to report this and found this old thread that was -- unbelievably -- still active. Fortunately for me, I saw the comments above that recommend using the --disable-server option. I added this to my script and now I can open terminals on both screens once again. Since the manpage says: -disable-server: Do not register with the D-BUS session message bus I'd say this pretty clearly points to a D-BUS problem. Would someone who in maintaining the terminal program check back regarding the history of D-BUS implementation back in 2013 onward and then coordinate to get this resolved. At the very least, deactivate the server option and allow it to be turned on if desired, in order to stop users from pulling out their hair. The amount of time wasted on this problem by me alone is ... a lot! Regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1243354 Title: Xfce4-terminal cannot run on more than one X screen at a time To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-terminal/+bug/1243354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789759] [NEW] All online manpages formatted very badly
Public bug reported: OS: Xubuntu 18.04 Tested browsers: Firefox 61.0.1, Chromium 68.0.3440.106 See: http://manpages.ubuntu.com/manpages/ In some recent attempt to reformat the Ubuntu online manual pages, some disastrous decisions were made. First, the overall appearance of the pages looks extremely childish. As with so many poor UI decisions being made by companies these days, most of the screen is now filled with white space rather than content. This doesn't improve readability, it just makes it harder to locate and read the content as so much scrolling is required. I strongly suggest a redesign that imposes some fundamental readability metrics. Much more importantly, there is a very serious bug which can be seen in the attached image. The text boxes which contain the section content for the man pages do not wrap the text. The content line lengths are fixed and force a horizontal scrollbar for any reasonable browser width that is not set to full-screen. This makes it next to impossible to read the content as you must scroll back and forth for every line! When I looked at the manpages using Opera 55.0.2994.44, there are not any scrollbars at all -- neither for the content boxes nor the page overall. Opera scrolling works fine for all other sites I visit. Please fix this ASAP. Thanks. ** Affects: synaptic (Ubuntu) Importance: Undecided Status: New ** Tags: manpage ubuntu ui-design ** Attachment added: "Example screenshot of a manual page" https://bugs.launchpad.net/bugs/1789759/+attachment/5182399/+files/ubuntu_02.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789759 Title: All online manpages formatted very badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1789759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754886] Re: Eclipse fails to start on fresh 18.04 installation
I don't understand how things as critical as this are not being fixed immediately? Netbeans also fails to start. This is a java problem in both cases. https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1775766 https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/1763091 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754886 Title: Eclipse fails to start on fresh 18.04 installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1754886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777296] [NEW] Synaptic scrollbar does not work properly
Public bug reported: Xubuntu 18.04 Synaptic 0.84.3 Many years ago this problem was reported and it still has not been addressed. The main scrollbar works opposite of almost all other scrollbars everywhere. If you B1 click in the scrollbar gutter (i.e., above or below the movable bar), the contents jumps to the current mouse position. If you B2 click in the gutter, the contents scrolls a page at a time. This B1 and B2 behavior should be flipped to agree with the world and make a predictable product. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777296 Title: Synaptic scrollbar does not work properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1777296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716749] Re: Synaptics is not fully aware of display environment
Well, it's 06-16-2018 and we're up to Xubuntu 18.04 and this problem has not been addressed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716749 Title: Synaptics is not fully aware of display environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1716749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776576] Re: Ubuntu 18.04 uograde: samba fails to run
Sorry for the delay in responding. Everything is finally resolved. Here is what I found. The Ubuntu OS was upgraded for a week and the system was rebooted multiple times before I noticed the samba problem. At that point, in addition to trying to start the samba-ad-dc service, I also had tried manually to start smbd and nmbd multiple times and received similar error messages with a failure of either starting. Since the services were not running there was no output in the /var/log/samba log files. Running testparm was showing no problems other than the unimportant warnings: rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) WARNING: The "syslog" option is deprecated neither of which should cause any problem. I do not believe that I changed anything significant, yet upon another system reboot both smbd and nmbd services started automatically and they continue to run properly upon subsequent reboots. I'm afraid I cannot explain why this is the case. Things like this are usually user error, but I cannot identify what may have been the problem. Now, the Ubuntu system could see the samba and external Windows shares. However, the Windows 10 machines could not see the samba server! This turned out to be due to a recent push of Windows 10 version 1803 which changed smb behavior by disabling the SMBv1 protocol, supporting only v2 and v3 by default. Now, why samba could not negotiate using these protocols is unclear, but the workaround was to re-enable SMBv1 on the Windows 10 machines, at which point they could negotiate with samba once again. A second difficulty was that it was impossible to connect to the samba server using the normal username and password that had worked in the past. The only solution I was able to discover was that the connection had to be established with hostname\username rather than username alone. Then everything was back to normal. Someone may want to take a look at Windows 10 v1803 to see how it is interacting with the standard samba configuration. In the future Microsoft may eliminate support for SMBv1 altogether. Sorry I don't have anything more definitive as to why smbd/nmbd were not running, but I really appreciate the feedback and support. Let me know if I can provide any additional useful information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776576 Title: Ubuntu 18.04 uograde: samba fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1776576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776576] Re: Ubuntu 18.04 uograde: samba fails to run
A slightly modified smb.conf for conceal some personal info. ** Attachment added: "smb.conf" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1776576/+attachment/5151907/+files/smb.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776576 Title: Ubuntu 18.04 uograde: samba fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1776576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776576] [NEW] Ubuntu 18.04 uograde: samba fails to run
Public bug reported: Samba has been running properly in all previous version of Xubuntu up through 17.10 with server role = standalone. After the 18.04 upgrade, all samba services fail to start as noted below. numerous changes were made, including advice from the net to add "client max protocol = NT1" to smb.conf, all with no success. A last-ditch attempt to reinstall the samba 2:4.7.6+dfsg~ubuntu-0ubuntu2 from synaptic fails with the pop-up error message: E: samba: installed samba package post-installation script subprocess returned error exit status 1 The log output is attached. An attempt to start the samba service: # service samba-ad-dc start Job for samba-ad-dc.service failed because the control process exited with error code. See "systemctl status samba-ad-dc.service" and "journalctl -xe" for details. # systemctl status samba-ad-dc.service ● samba-ad-dc.service Loaded: masked (/dev/null; bad) Active: failed (Result: exit-code) since Tue 2018-06-12 15:34:02 PDT; 17min ago Main PID: 27780 (code=exited, status=1/FAILURE) Status: "daemon failed to start: Samba detected misconfigured 'server role' and exited. Check logs for details" Jun 12 15:34:02 dymaxion.cjsa2.com systemd[1]: Starting Samba AD Daemon... Jun 12 15:34:02 dymaxion.cjsa2.com samba[27780]: handle_name_resolve_order: WARNING: Ignoring invalid list value ' Jun 12 15:34:02 dymaxion.cjsa2.com systemd[1]: samba-ad-dc.service: Main process exited, code=exited, status=1/FAI Jun 12 15:34:02 dymaxion.cjsa2.com systemd[1]: samba-ad-dc.service: Failed with result 'exit-code'. Jun 12 15:34:02 dymaxion.cjsa2.com systemd[1]: Failed to start Samba AD Daemon. # A second (and subsequent) attempt to start samba: # service samba-ad-dc start Failed to start samba-ad-dc.service: Unit samba-ad-dc.service is masked. I tried a number of options to unmask and start the samba services with no success. Many people seem to be having great difficulty with samba now, but I located no clear instructions for addressing the problem which seems might be related to the active directory component. I would expect an upgrade to a properly configured system to continue to run. I'm guessing that there is a fundamental configuration problem here, but possibly a deeper level bug. I will also attach the smb.conf. file to this report. Guidance is appreciated. ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: 18.04 samba xubuntu ** Attachment added: "Samba package installation log" https://bugs.launchpad.net/bugs/1776576/+attachment/5151906/+files/samba -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776576 Title: Ubuntu 18.04 uograde: samba fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1776576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775770] [NEW] netbeans runtime error
Public bug reported: As with eclipse, netbeans was running under 17.10 but fails after the 18.04 upgrade. When started as either: /usr/bin/netbeans or /usr/bin/netbeans --jdkhome /usr/lib/jvm/default-java (NOTE: default-java points to java-1.11.0-openjdk-amd64) It generates the following error and exits: WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.netbeans.ProxyURLStreamHandlerFactory (file:/usr/share/netbeans/platform18/lib/boot.jar) to field java.net.URL.handler WARNING: Please consider reporting this to the maintainers of org.netbeans.ProxyURLStreamHandlerFactory WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release This is netbeans 8.1+dfsg3-4 ** Affects: netbeans (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775770 Title: netbeans runtime error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/1775770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775766] [NEW] eclipse java runtime error error
Public bug reported: Eclipse was running properly under 17.10. After the upgrade to 18.04, attempts to start it produce the following error: !SESSION Thu Jun 07 22:26:49 PDT 2018 -- !ENTRY org.eclipse.equinox.launcher 4 0 2018-06-07 22:26:49.702 !MESSAGE Exception launching the Eclipse Platform: !STACK java.lang.ClassNotFoundException: org.eclipse.core.runtime.adaptor.EclipseStarter at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:466) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:566) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:626) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) at org.eclipse.equinox.launcher.Main.run(Main.java:1438) at org.eclipse.equinox.launcher.Main.main(Main.java:1414) I have reinstalled all the eclipse and core java packages with no improvement. eclipse 3.8.1-11 libcj-java 3.13.3-1 java-common 0.63ubuntu1~02 default-jre 2:1.10-63ubuntu1~02 default-jdk 2:1.10-63ubuntu1~02 ** Affects: eclipse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775766 Title: eclipse java runtime error error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1775766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775347] Re: Upgrade to 18.04 caused wrong graphics driver to be installed
The update status link in the above comment does not work. I don't see an option on this page to update/edit the status. This seems like an installation issue and not something related to a package, but if I had to select a package related to this, I would say: nvidia-driver-390 390.48-0ubuntu3 NVIDIA driver metapackage I hope that helps and that someone can assign this info to the package section. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775347 Title: Upgrade to 18.04 caused wrong graphics driver to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1775347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775349] Re: services(5) manual page formatting is screwed up for bionic
Also: netstt(8), route(8), ufw(8), iptables(8), etc. etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775349 Title: services(5) manual page formatting is screwed up for bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1775349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775349] Re: services(5) manual page formatting is screwed up for bionic
Same problem with service(8) manpage. Someone should bake a full check of the manual pages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775349 Title: services(5) manual page formatting is screwed up for bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1775349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775347] [NEW] Upgrade to 18.04 caused wrong graphics driver to be installed
Public bug reported: Upgrading Xubuntu 17.10 to 18.04 Using Nvidia Quadro K4000 Graphics Card with proprietary driver and dual screens After the upgrade, which went smoothly, only one screen was recognized and the system was almost unusable. The Xorg process was running wild, consuming almost all the CPU. It was difficult to move the cursor and all screen updates were incredibly slow. I suspected the graphics driver and saw that the Nvidia driver had been replaced with the X.Org Nouveau open source driver. I checked the available drivers with: 7-> ubuntu-drivers devices == /sys/devices/pci:00/:00:03.0/:04:00.0 == modalias : pci:v10DEd11FAsv10DEsd097Cbc03sc00i00 vendor : NVIDIA Corporation model: GK106GL [Quadro K4000] driver : nvidia-driver-390 - distro non-free recommended driver : nvidia-340 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin After reinstalling the proprietary driver with the command: 8-> sudo apt install nvidia-driver-390 and rebooting the system, everything was back to normal. I have had similar driver replacement problems with past upgrades. Why doesn't the upgrade register and reinstall the proper graphics driver? And why is the default driver so abysmal with a standard Nvidia card? This should be fixed in future upgrades. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: driver nvidia xubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775347 Title: Upgrade to 18.04 caused wrong graphics driver to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1775347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775349] [NEW] services(5) manual page formatting is screwed up for bionic
Public bug reported: See: http://manpages.ubuntu.com/manpages/bionic/en/man5/services.5.html The formatting for this page is bad. It was OK in artful. See attached image. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "Screenshot of services(5) manpage" https://bugs.launchpad.net/bugs/1775349/+attachment/5149229/+files/Screenshot_2018-06-06_01-00-30.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775349 Title: services(5) manual page formatting is screwed up for bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1775349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725954] Re: It is hard and nonintuitive to switch to console ttys on Ubuntu 17.10
Turns out this is the default for gdm. According to this blog post: http://rubereality.com/2012/11/08/change-the-vt-setup-with-gdm-3-6-1-and-systemd/ (Wayback Machine: https://web.archive.org/web/20141228051646/http://rubereality.com/2012/11/08/change-the-vt-setup-with-gdm-3-6-1-and-systemd/ ) changing it back to previous behaviour will require recompiling gdm :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725954 Title: It is hard and nonintuitive to switch to console ttys on Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slick-greeter/+bug/1725954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725954] Re: It is hard and nonintuitive to switch to console ttys on Ubuntu 17.10
The fact that Ctrl-Alt-F1 now brings up the login screen is documented: https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes#Ubuntu_Desktop "GDM has replaced LightDM as the default display manager. The login screen now uses virtual terminal 1 instead of virtual terminal 7." (Ctrl-Alt-F1 switches to virtual terminal 1.) I've been looking for a way to switch back to having 6 text terminals but I haven't been successful. I've tried uncommenting "NAutoVTs=6" and "ReserveVT=6" in /etc/systemd/logind.conf but it had no effect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725954 Title: It is hard and nonintuitive to switch to console ttys on Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slick-greeter/+bug/1725954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716749] [NEW] Synaptics is not fully aware of display environment
Public bug reported: In a dual monitor environment where separate Xfce4 desktops are running on each monitor, you can start Synaptic in either desktop environment, but if you start it on display :0.1, it shows the Authenticate pop-up window on display :0.0. Once the password is entered, the main window will then appear on display :0.1. All the components of a given program should be display-environment-aware. There are a number of system applications that have similar problems. I'll report them as I continue to encounter this problem. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Sep 12 11:21:53 2017 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/ksh SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to zesty on 2017-05-27 (108 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716749 Title: Synaptics is not fully aware of display environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1716749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1524755] Re: systemd support
thanks for digging up a 2 year old problem holy hell -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1524755 Title: systemd support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/1524755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1524755] Re: systemd support
I setup this bug because it was causing mate-panel to lock up and crash the whole desktop just because systemd is garbage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1524755 Title: systemd support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/1524755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697309] [NEW] package apport 2.20.4-0ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: >From what I can tell, this error message randomly pops up from time to time. >nothing terribly bad happens as it does not seem to affect anything critical. >though the popup message is a tad annoying. this is Ubuntu 17.04 btw. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: apport 2.20.4-0ubuntu4.1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: wl ApportLog: ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: libtasn1-6:amd64: Install NULL: ConfigurePending Architecture: amd64 CrashReports: 600:0:116:85927:2017-06-05 15:56:55.945291042 -0700:2017-06-05 15:56:56.945291042 -0700:/var/crash/apport.0.crash 640:1000:116:7748570:2017-06-06 16:17:47.081461668 -0700:2017-06-06 16:17:48.081461668 -0700:/var/crash/_usr_share_hplip_systray.py.1000.crash Date: Mon Jun 5 15:56:56 2017 DpkgHistoryLog: Start-Date: 2017-06-05 15:56:55 Commandline: /usr/bin/unattended-upgrade Upgrade: libtasn1-6:amd64 (4.10-1, 4.10-1ubuntu0.1) DuplicateSignature: package:apport:2.20.4-0ubuntu4.1 Processing triggers for libc-bin (2.24-9ubuntu2) ... dpkg: error processing package apport (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-03-08 (95 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: apport Title: package apport 2.20.4-0ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to zesty on 2017-05-09 (33 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697309 Title: package apport 2.20.4-0ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1697309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
I have been running this kernel a 3-4 days now without any problems. root@merlin:~# uname -a Linux merlin 4.10.8-041008-generic #201703310531 SMP Fri Mar 31 09:33:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux root@merlin:~# cat /boot/config-$(uname -r) |grep CONFIG_MIGRATION CONFIG_MIGRATION=y Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
I've been working pretty heavily throughout the day (Eclipse, Chrome, Thunderbird, MySQL, etc) with the 4.10.0-8 and haven't hit the bug. I will run a couple more days on this version and see if it pops up. painter@merlin:~$ uname -a Linux merlin 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:04:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux painter@merlin:~$ uptime 16:48:33 up 6:59, 1 user, load average: 0.36, 0.52, 0.64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
Trying to test as recommended and installed linux-image-4.10.0-8-generic_4.10.0-8.10_amd64.deb linux-image-extra-4.10.0-8-generic_4.10.0-8.10_amd64.deb Note to others, if you are using any proprietary drivers, you should also download and install both: linux-headers-4.10.0-8_4.10.0-8.10_all.deb linux-headers-4.10.0-8-generic_4.10.0-8.10_amd64.deb Required to continue using VirtualBox but will need to run /sbin/vboxconfig after installing. I will try this one out for today and post back my results this afternoon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
I can report that mainline seems fine. I have not tried 4.10.11 but stopped at 4.10.8 as it is working well for me the past couple days. painter@merlin:~$ uname -a Linux merlin 4.10.8-041008-generic #201703310531 SMP Fri Mar 31 09:33:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux painter@merlin:~$ uptime 17:41:20 up 11:09, 1 user, load average: 0.20, 0.06, 0.02 No more crashes! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682184] Re: Kernel bug 4.10.0-19-generic causing lockup and crash on Ubuntu 17.04-beta2
I installed v4.10.8 and left stress running on for about an hour. Just got back and the system has been stable for the past 5 hours without any failures. painter@merlin:~$ uname -a Linux merlin 4.10.8-041008-generic #201703310531 SMP Fri Mar 31 09:33:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux painter@merlin:~$ uptime 23:46:02 up 5:07, 1 user, load average: 0.19, 0.08, 0.01 Leaving tomorrow morning on vacation, so if you want me to test anything else, it will have to be when I get back next Monday. Thanks! Jeff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682184 Title: Kernel bug 4.10.0-19-generic causing lockup and crash on Ubuntu 17.04-beta2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682184] Re: Kernel bug 4.10.0-19-generic causing lockup and crash on Ubuntu 17.04-beta2
So far I have test v4.10.2, v4.10.4 and v4.10.6 - each time running Thunderbird, Chrome, RhythmBox, Eclipse and then starting up stress to push a system load (20-25 minutes each). I originally saw some funky performance within the first few minutes with the kernel that started this thread, but so far I haven't seen any issues. I will test v4.10.8 next and see if it breaks. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682184 Title: Kernel bug 4.10.0-19-generic causing lockup and crash on Ubuntu 17.04-beta2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682184] Re: Kernel bug 4.10.0-19-generic causing lockup and crash on Ubuntu 17.04-beta2
I will try to see what I can do. Leaving town tomorrow for a long weekend. If not, I can work on it Sunday when I get back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682184 Title: Kernel bug 4.10.0-19-generic causing lockup and crash on Ubuntu 17.04-beta2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682184] Re: Kernel bug 4.10.0-19-generic causing lockup and crash on Ubuntu 17.04-beta2
Mainline v4.10 seems to have fixed the issue. However, now I am getting a Bluetooth error on startup. This does not seem to impact actual use though as I can still do an audio sync and stream to my main receiver. Up and running for over an hour with VirtualBox, MySQL, Eclipse, Thunderbird and Chrome operating smoothly (I am primarily a Java developer). painter@merlin:~$ uname -a Linux merlin 4.10.0-041000-generic #201702191831 SMP Sun Feb 19 23:33:19 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux painter@merlin:~$ uptime 14:44:22 up 1:11, 1 user, load average: 0.28, 0.20, 0.16 This kernel is also working nicely with the NVIDIA drivers (the 4.11 wouldn't load). Thanks! --- blue tooth error from dmesg --- [2.667708] Bluetooth: Core ver 2.22 [2.667723] Bluetooth: HCI device and connection manager initialized [2.667725] Bluetooth: HCI socket layer initialized [2.667726] Bluetooth: L2CAP socket layer initialized [2.667729] Bluetooth: SCO socket layer initialized [2.676237] Bluetooth: HCI UART driver ver 2.3 [2.676238] Bluetooth: HCI UART protocol H4 registered [2.676239] Bluetooth: HCI UART protocol BCSP registered [2.676239] Bluetooth: HCI UART protocol LL registered [2.676239] Bluetooth: HCI UART protocol ATH3K registered [2.676240] Bluetooth: HCI UART protocol Three-wire (H5) registered [2.676263] Bluetooth: HCI UART protocol Intel registered [2.676274] Bluetooth: HCI UART protocol Broadcom registered [2.676275] Bluetooth: HCI UART protocol QCA registered [2.676275] Bluetooth: HCI UART protocol AG6XX registered [2.676275] Bluetooth: HCI UART protocol Marvell registered [3.150833] usb 1-11: Product: Bluetooth Radio [3.867221] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723 [3.867223] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_config.bin [3.873474] bluetooth hci0: Direct firmware load for rtl_bt/rtl8723b_config.bin failed with error -2 [3.873476] Bluetooth: hci0: Failed to load rtl_bt/rtl8723b_config.bin [3.874030] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_fw.bin [3.877009] Bluetooth: hci0: rom_version status=0 version=1 [3.877012] Bluetooth: cfg_sz 0, total size 22496 [3.928766] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [3.928767] Bluetooth: BNEP filters: protocol multicast [3.928769] Bluetooth: BNEP socket layer initialized [ 16.792458] Bluetooth: RFCOMM TTY layer initialized [ 16.792467] Bluetooth: RFCOMM socket layer initialized [ 16.792477] Bluetooth: RFCOMM ver 1.11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682184 Title: Kernel bug 4.10.0-19-generic causing lockup and crash on Ubuntu 17.04-beta2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682184] Re: Kernel bug 4.10.0-19-generic causing lockup and crash on Ubuntu 17.04-beta2
I've installed the v4.10 mainline. painter@merlin:~$ uname -a Linux merlin 4.10.0-041000-generic #201702191831 SMP Sun Feb 19 23:33:19 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Will monitor and see if there are any more system crashes. I will update in a few hours. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682184 Title: Kernel bug 4.10.0-19-generic causing lockup and crash on Ubuntu 17.04-beta2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682184] Re: Kernel bug 4.10.0-19-generic causing lockup and crash on Ubuntu 17.04-beta2
I had another system crash last night, and two this morning. I then installed the daily mainline kernel and have been running for a few hours without any issues. I think this issue is resolved in the updated kernel. painter@merlin:~$ uname -a Linux merlin 4.11.0-999-generic #201704122202 SMP Thu Apr 13 02:04:09 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682184 Title: Kernel bug 4.10.0-19-generic causing lockup and crash on Ubuntu 17.04-beta2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682184] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1682184/+attachment/4860866/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682184 Title: Kernel bug 4.10.0-19-generic causing lockup and crash on Ubuntu 17.04-beta2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
