[Desktop-packages] [Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as
using mutter Version: 3.34.3-1ubuntu1~19.10.1 I can systematically reproduce the crash with the following steps: install intellij-idea open a java project press F4 to open project settings select SDK click + to add a new SDK and select JDK -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1845281 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "code should not be reached"] Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Fix Committed Bug description: [ Description ] Intellij and other java apps can cause GNOME shell to crash [ Test case ] 1) Run this test case: https://gitlab.gnome.org/3v1n0/mutter/snippets/956 2) Windows should appear and close correctly while Gnome shell must not crash [ Regression potential ] Parent-child relationship on some windows might be broken. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1845281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846899] Re: X won't start at boot with either nvidia driver on GeForce GT 730 (bionic)
** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Won't Fix ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1846899 Title: X won't start at boot with either nvidia driver on GeForce GT 730 (bionic) Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Won't Fix Bug description: The video card is a GeForce GT 730, which worked well with Ubuntu 16.04. After changing to Xubuntu 18.04, I can only run the Nouveau driver and the lack of acceleration is quite noticeable. When I try to enable the "tested" NVidia driver (390), the system never presents a log-in prompt, I just get a colorful display of large blinking gibberish. I have to go to the boot options, go directly to root prompt, and remove the NVidia driver. This make the system usable again, but I'm back to the Nouveau driver. I get similar symptoms with version 340.107 of the NVidia driver. It's a little hard to collect debug information when I can't get to a prompt to look at log files... Suggestions are welcome. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None Date: Sat Oct 5 13:56:41 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF108 [GeForce GT 730] [19da:8199] InstallationDate: Installed on 2019-04-13 (175 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=d19b5e72-689e-4877-93dd-0d4bf5f7cc98 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4024 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4024:bd09/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Oct 5 13:56:03 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1846899/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850651] Re: [SRU] Authentication constantly re-requested for Google
** Changed in: thunderbird (Ubuntu Xenial) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1850651 Title: [SRU] Authentication constantly re-requested for Google Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Xenial: Fix Committed Status in thunderbird source package in Bionic: Fix Committed Status in thunderbird source package in Disco: Fix Committed Status in thunderbird source package in Eoan: Fix Committed Status in thunderbird source package in Focal: Fix Released Bug description: [Impact] A recent server-side change with google e-mail accounts (gmail) means that thunderbird consistently fails to authenticate, prompting for the user's e-mail address and password over and over, without ever succeeding. This has been fixed upstream and is tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=1592407. [Test Case] In a clean environment, launch thunderbird and add an existing gmail account. Thunderbird should auto-detect all the relevant parameters, and then an external webview should pop up to prompt for your e-mail address (it's not auto-filled, that's a separate issue that's also known upstream) and your password. After filling this in and authorizing thunderbird to access your e-mails, your account should be set up and thunderbird should start fetching e-mails from your inbox. Instead it fails to authenticate and displays the authentication pop up again. [Regression Potential] Low, as this is an official upstream point release that addresses only this regression (see https://www.thunderbird.net/en-US/thunderbird/60.9.1/releasenotes/). The fix is minimal and self-contained (https://hg.mozilla.org/releases/comm-esr60/rev/56b6d1b50647143c25efe642b37b02f65f9c4343), if the bug is indeed confirmed to be fixed then it should be safe. [Original Bug Description] When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. I am using OAuth2 (so this ( https://support.mozilla.org/en- US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3444 F pulseaudio /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-03 (817 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090404 RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.9-0ubuntu4 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-05-22 (161 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8
[Desktop-packages] [Bug 1813479] Re: "appstreamcli refresh-cache" does not work without shared-mime-info
This bug was fixed in the package appstream - 0.12.10-1 --- appstream (0.12.10-1) unstable; urgency=medium * New upstream version: 0.12.10 * appstream: Depend on shared-mime-info explicitly (LP: #1813479) * Update build dependencies (added libsoup2.4-dev) * Update symbols file * less-long-token-noise.patch: Make less noise when encountering excessively long search tokens (Closes: #942438) * Flag d/rules as not requiring root * Bump standards version: No changes needed -- Matthias Klumpp Sat, 18 Jan 2020 18:58:00 +0100 ** Changed in: appstream (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1813479 Title: "appstreamcli refresh-cache" does not work without shared-mime-info Status in appstream package in Ubuntu: Fix Released Bug description: Steps to reproduce: $ sudo apt-get install appstream $ sudo appstreamcli refresh-cache --force --verbose AppStream cache update completed successfully. # (it works good, because shared-mime-info is installed by default in Ubuntu) $ sudo apt-get remove shared-mime-info $ sudo apt-get remove --purge shared-mime-info $ sudo appstreamcli refresh-cache --force --verbose ** (appstreamcli:21810): DEBUG: 15:55:46.549: Reading: /var/lib/app-info/yaml/mirror.yandex.ru_ubuntu_dists_bionic_main_dep11_Components-amd64.yml.gz ** (appstreamcli:21810): DEBUG: 15:55:46.550: WARNING: Invalid DEP-11 file found. Could not parse YAML: control characters are not allowed # ... many lines with errors ... AppStream system cache was updated, but problems were found: Metadata files have errors: [big list of files] I think this is just a missing dependency, just add shared-mime-info as a dependency for appstream or libappstream4 package Ubuntu version (maybe cosmic is also affected, I didn't test it): $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 appstream version: $ dpkg -s libappstream4 | grep -i version Version: 0.12.0-3ubuntu1 $ dpkg -s appstream | grep -i version Version: 0.12.0-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1813479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1777285]
[Automated Action] NeedInfo-To-Unconfirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1777285 Title: Batch libreoffice --convert-to offers no way to wait for document completion Status in LibreOffice: New Status in libreoffice package in Ubuntu: Confirmed Bug description: Command-line: libreoffice --convert-to odt:writer8 myfile.txt The returned status code ($?) is zero. So far, so good. But, when I try to access the ODT file (E.g. copy it), it doesn't yet exist. Adding `sync; sync; sync` right after the libreoffice batch execution did not help. Adding --headless as an option did not help. If I sleep for a few seconds immediately after the libreoffice batch execution, then the file finally gets completed before a subsequent command references the ODT file. Sample script: ### Create somehow a file called myfile.txt rm myfile.odt somewhere-else.odt libreoffice --headless --convert-to odt:writer8 myfile.txt RC=$? if [ $RC -ne 0 ]; then echo '*** libreoffice conversion failed for myfile.txt' exit 86 fi #sleep 3 ls *.odt Result: ls: cannot access '*.odt': No such file or directory If one changes the above script so that the sleep is executed, then the ODT file is available. Observation: It appears that executing libreoffice in batch mode is somehow kicking off a separate process to finish the ODT file. The exit to the shell and the availability of the ODT file should be synchronized. Before 18.04, I never saw this behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jun 16 17:07:02 2018 InstallationDate: Installed on 2017-10-13 (246 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-18 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1777285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1777285]
@Xisco Faulí - Are you asking me to download and build LibreOffice for that one source change? I wouldn't know where to begin. I am a developer but up to my eyeballs in Astrophysics projects at the moment. Is there anyone on the development or testing team who already has the source downloaded and knows how to build LibreOffice? I am confident that such a person could easily reproduce this anomaly on Linux, Android, or Unix with the script I provided. Then, make the change I suggested. Re-run the script and see that the anomaly disappears. Also, after a change like this, wouldn't one need to run your standard regression test suite? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1777285 Title: Batch libreoffice --convert-to offers no way to wait for document completion Status in LibreOffice: New Status in libreoffice package in Ubuntu: Confirmed Bug description: Command-line: libreoffice --convert-to odt:writer8 myfile.txt The returned status code ($?) is zero. So far, so good. But, when I try to access the ODT file (E.g. copy it), it doesn't yet exist. Adding `sync; sync; sync` right after the libreoffice batch execution did not help. Adding --headless as an option did not help. If I sleep for a few seconds immediately after the libreoffice batch execution, then the file finally gets completed before a subsequent command references the ODT file. Sample script: ### Create somehow a file called myfile.txt rm myfile.odt somewhere-else.odt libreoffice --headless --convert-to odt:writer8 myfile.txt RC=$? if [ $RC -ne 0 ]; then echo '*** libreoffice conversion failed for myfile.txt' exit 86 fi #sleep 3 ls *.odt Result: ls: cannot access '*.odt': No such file or directory If one changes the above script so that the sleep is executed, then the ODT file is available. Observation: It appears that executing libreoffice in batch mode is somehow kicking off a separate process to finish the ODT file. The exit to the shell and the availability of the ODT file should be synchronized. Before 18.04, I never saw this behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jun 16 17:07:02 2018 InstallationDate: Installed on 2017-10-13 (246 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-18 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1777285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1777285]
(In reply to Richard Elkins from comment #9)
> The source code indicates that soffice.bin is the one starting a background
> process that does not finish before soffice.bin exits.
>
> See:
> https://github.com/LibreOffice/core/blob/master/shell/source/unix/exec/
> shellexec.cxx
> Go to line 218:
>
> OString cmd =
> #ifdef LINUX
> // avoid blocking (call it in background)
> "( " + aBuffer.makeStringAndClear() + " ) &";
> #else
> aBuffer.makeStringAndClear();
> #endif
> FILE *pLaunch = popen(cmd.getStr(), "w");
> if ( pLaunch != nullptr )
> {
> if ( 0 == pclose( pLaunch ) )
> return;
>
> It would be interesting to understand why execution is in background *only*
> for Linux. In my opinion, it is undesirable for command line execution in
> any O/S.
>
> Other opinions? It is possible for me to be perfectly content with the
> artificial `sleep N` in my shell script.
it was added in
https://cgit.freedesktop.org/libreoffice/core/commit/?id=f5fe1aa1 to fix
bug 32427
@Richard, can you confirm removing the mentioned ifdef condition would
fix the issue? In that case we could submit a patch removing it. Most
likely bug 32427 is obsolete nowadays...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1777285
Title:
Batch libreoffice --convert-to offers no way to wait for document
completion
Status in LibreOffice:
New
Status in libreoffice package in Ubuntu:
Confirmed
Bug description:
Command-line: libreoffice --convert-to odt:writer8 myfile.txt
The returned status code ($?) is zero. So far, so good. But, when I
try to access the ODT file (E.g. copy it), it doesn't yet exist.
Adding `sync; sync; sync` right after the libreoffice batch execution did not
help.
Adding --headless as an option did not help.
If I sleep for a few seconds immediately after the libreoffice batch
execution, then the file finally gets completed before a subsequent
command references the ODT file.
Sample script:
### Create somehow a file called myfile.txt
rm myfile.odt somewhere-else.odt
libreoffice --headless --convert-to odt:writer8 myfile.txt
RC=$?
if [ $RC -ne 0 ]; then
echo '*** libreoffice conversion failed for myfile.txt'
exit 86
fi
#sleep 3
ls *.odt
Result: ls: cannot access '*.odt': No such file or directory
If one changes the above script so that the sleep is executed, then
the ODT file is available.
Observation: It appears that executing libreoffice in batch mode is
somehow kicking off a separate process to finish the ODT file. The
exit to the shell and the availability of the ODT file should be
synchronized.
Before 18.04, I never saw this behavior.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice 1:6.0.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Jun 16 17:07:02 2018
InstallationDate: Installed on 2017-10-13 (246 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to bionic on 2018-05-18 (29 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1777285/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844453]
*** Bug 127662 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1844453
Title:
[upstream] Access to the Google remote account does not work
Status in LibreOffice:
Confirmed
Status in libreoffice package in Ubuntu:
Confirmed
Bug description:
I have a Google account with 2FA login, from LibreOffice I try to add the
remote account, but it doesn't work, it asks me for a 6-digit PIN.
Investigating to see if it was just my problem, I discovered that this is a
long-standing LibreOffice bug (1) and seems unresolved.
The last report confirms this: "2019-07-04 04:44:41 UTC
This feature doesn't work with my Google account _w/o_
2FA.
Bug hasn't be resolved for about 3 years and "very soon"
we may celebrate 5 years anniversary. %-("
1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 17 23:00:10 2019
InstallationDate: Installed on 2019-02-18 (210 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1844453/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
thanks for testing! ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken Status in xserver-xorg-driver-ati: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu source package in Bionic: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati source package in Bionic: Invalid Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati source package in Eoan: Fix Released Status in xserver-xorg-video-ati package in Fedora: Fix Released Bug description: [Impact] Combo boxes are broken (cf screenshot) Tested in gnome-control-center and gtk3-demo. Tooltips are also garbage. [Test case] Install the updated package, test tooltips that they display fine. [Regression potential] This is a single commit backport from upstream, so there shouldn't be any regression potential To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1841718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848522] Re: Backport packages for 18.04.4 HWE stack
the ati/amdgpu drivers were for bug 1841718, which got verified ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1848522 Title: Backport packages for 18.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-9 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-9 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-9: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.2.x series, so there shouldn't be any regressions left at that point xserver: a new git snapshot (or maybe a point-release) xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 559331] Re: Permanent "Printer-out-of-paper" message.
There is a large printer in our office that have 4 trays, there are 2 trays that is always empty, and I think it is passing the out-of-paper error status to the CUPS. It can still print anyway, just the out-of- paper error status stuck in the ubuntu printer GUI with a red (-) mark. Is there anyway to ignore several trays producing such error? Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/559331 Title: Permanent "Printer-out-of-paper" message. Status in cups package in Ubuntu: Confirmed Bug description: Binary package hint: cups This probably has to do with CUPS. Version: 1.4.1- 4ubuntu2.4 (latest on Karmic). I was printing a document when the printer was out of paper and got a message that "The printer is out of paper". I went to reload it and clicked resume on the printer and printing carried on normally. From this point on, the message "The printer is out of paper" is permanently stuck on the printer. - Every time i print, i get the message "The printer is out of paper", but the printing occurs without errors. - The configuration tool (system-config-printer 1.1.12) shows the printer with the red error sign. When viewing the properties of said printer, in the "Ink/Toner Levels" section, i have the "Status Message": "Printer HP-Officejet-Pro-k550 is out of paper". If i click refresh then i get a "CUPS server error": "There was an error during the CUPS operation: 'client-error-document-format-not-supported'." (Not sure this is relevant). Removing and reinstalling the printer fixes this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/559331/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860308] Re: After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts
*** This bug is a duplicate of bug 1851162 ***
https://bugs.launchpad.net/bugs/1851162
** This bug is no longer a duplicate of bug 1860316
After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts
** This bug has been marked a duplicate of bug 1851162
nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 [error:
redefinition of ‘list_is_first’]
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1860308
Title:
After upgrade 19.01.2020 display resolution only 640x480. Lubuntu
18.04 lts
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
Hello!
Yesterday, 01/19/2020, I updated my Lubuntu 18.04 lts. After restarting, the
display resolution is only 640x480. I want to set a different resolution, but
there are no other options.
I restored Lubuntu from backup to Clonesilla. New OSs work correctly, but
after updating the problem appears again.
Здравствуйте!
Вчера, 19.01.2020, я обновил свою Lubuntu 18.04 lts. После перезапуска
разрешение на дисплее только 640х480. Я хочу установить другое разрешение, но
других вариантов нет.
Я восстановил Lubuntu из резервной копии в Сlonesilla. Новые ОС работают
корректно, но после обновления проблема появляется снова.
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.3.0-26-generic.
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: VT1705 Analog [VT1705 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: a 936 F pulseaudio
/dev/snd/controlC0: a 936 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf720 irq 28'
Mixer name : 'VIA VT1705'
Components : 'HDA:11064397,15658110,0010'
Controls : 37
Simple ctrls : 19
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17'
Mixer name : 'Nvidia GPU 14 HDMI/DP'
Components : 'HDA:10de0014,10de0101,00100100'
Controls : 28
Simple ctrls : 4
CurrentDesktop: LXDE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-28 (297 days ago)
InstallationMedia: Lubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
Package: pulseaudio 1:11.1-1ubuntu7.4
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
Tags: bionic
Uname: Linux 5.3.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/02/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: None
dmi.board.name: H61MLV2
dmi.board.vendor: BIOSTAR Group
dmi.board.version: 6.0
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.chassis.version: 6.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/02/2012:svnBIOSTARGroup:pnH61MLV2:pvr6.0:rvnBIOSTARGroup:rnH61MLV2:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0:
dmi.product.family: None
dmi.product.name: H61MLV2
dmi.product.sku: None
dmi.product.version: 6.0
dmi.sys.vendor: BIOSTAR Group
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1860308/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860316] Re: After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts
*** This bug is a duplicate of bug 1851162 *** https://bugs.launchpad.net/bugs/1851162 Thanks. It just sounds like this is bug 1851162 and you haven't yet found an effective way to recover from it. Sorry. :( ** This bug has been marked a duplicate of bug 1851162 nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 [error: redefinition of ‘list_is_first’] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1860316 Title: After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello! Yesterday, 01/19/2020, I updated my Lubuntu 18.04 lts. After restarting, the display resolution is only 640x480. I want to set a different resolution, but there are no other options. I restored Lubuntu from backup to Clonesilla. New OS work correctly, but after updating the problem appears again. Здравствуйте! Вчера, 19.01.2020, я обновил свою Lubuntu 18.04 lts. После перезапуска разрешение на дисплее только 640х480. Я хочу установить другое разрешение, но других вариантов нет. Я восстановил Lubuntu из резервной копии в Сlonesilla. Новые ОС работают корректно, но после обновления проблема появляется снова. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Jan 20 14:34:36 2020 InstallationDate: Installed on 2019-03-28 (297 days ago) InstallationMedia: Lubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1860316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860235] Re: totem crashed with SIGSEGV in g_mount_spec_get()
Thanks. Though since there have only been a couple dozen instances of this crash in the past 5 years I think Low priority is most appropriate. Sounds like it relates to using totem over SMB mounts?.. ** Changed in: gvfs (Ubuntu) Importance: Undecided => Medium ** Changed in: gvfs (Ubuntu) Status: New => Confirmed ** Changed in: gvfs (Ubuntu) Status: Confirmed => Triaged ** Changed in: totem (Ubuntu) Status: Confirmed => Triaged ** Changed in: gvfs (Ubuntu) Importance: Medium => Low ** Changed in: totem (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1860235 Title: totem crashed with SIGSEGV in g_mount_spec_get() Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Status in totem package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/4ef67c07533ef05b6c12894767e604456aca3ace https://gitlab.gnome.org/GNOME/gvfs/issues/446 --- I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi PC (0x7ff6dc45dd09) ok source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (412 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1860235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860175] Re: Ability to rearrange applet icons by drag/drop.
OK, we will need to assign this bug to all the extensions that might be affected. I don't believe gnome-shell itself can help here. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid ** Also affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1860175 Title: Ability to rearrange applet icons by drag/drop. Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Gnome 3.34.1 3) Ability to drag/drop applet icons to different places on the top bar. 4) Unable to drag/drop applet icons. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1860175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
Please don't run apport-collect on bugs you don't own. Please also avoid attaching crash files to bugs as we can't process them that way. You should run this command to create a new bug for each crash file: ubuntu-bug YOURFILE.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1152137] Re: Pulseaudio won't start when home directory not owned by user
Great, thanks.
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => Nick Moriarty (nick-moriarty)
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed => Triaged
** Tags added: fixed-in-14.0 fixed-upstream
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1152137
Title:
Pulseaudio won't start when home directory not owned by user
Status in pulseaudio package in Ubuntu:
Triaged
Bug description:
I have an NFS mounted home directory on a dedicated fileserver which is
shared with Windows PCs via SMB.
The home directory is not owned by me. ACLs are set on it to allow me
full control of the contents but prevent me from changing its permissions.
This means any files or directories created in the home directory are owned
by me even though the top level is not.
Pulseaudio checks the home directory is owned by the user at startup and
exits if it isn't. This stops it running on my system.
I have recompiled pulseaudio without this check and it works fine.
Please either remove or modify the following startup check:
pulseaudio-1.1/src/pulsecore/src/pulsecore/core-util.c line 1415:
if (st.st_uid != getuid()) {
pa_log_error("Home directory %s not ours.", h);
errno = EACCES;
goto finish;
}
A better check would be for pulseaudio to try and create the files/folders it
needs and fail if it cannot.
I am using Ubuntu 12.04 and pulseaudio 1:1.1-0ubuntu15.2.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1152137/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860175] Re: Ability to rearrange applet icons by drag/drop.
I think some are app indicators and some are from extensions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1860175 Title: Ability to rearrange applet icons by drag/drop. Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: 1) Ubuntu 19.10 2) Gnome 3.34.1 3) Ability to drag/drop applet icons to different places on the top bar. 4) Unable to drag/drop applet icons. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1860175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796437] Re: [nouveau] Xorg crashes with assertion failure "key->initialized" in dixGetPrivateAddr() from dixLookupPrivate() from DRI2Authenticate()
*** This bug is a duplicate of bug 1745345 *** https://bugs.launchpad.net/bugs/1745345 I run into this on Ubuntu Budgie 20.04 when trying to open GNOME Settings. It dumps me to to the login screen. I just tried to use About and it did the same thing. This is in a VirtualBox virtual machine if that is relevant. Happy to provide additional detail if needed. Thanks for looking into this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1796437 Title: [nouveau] Xorg crashes with assertion failure "key->initialized" in dixGetPrivateAddr() from dixLookupPrivate() from DRI2Authenticate() Status in xorg-server package in Ubuntu: Confirmed Bug description: Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared. Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 budgie-welcome: Installed: (none) Candidate: 0.6.1 Version table: 0.6.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages Seems to not be installed on a fresh install. So solved but needs fixing? ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. BootLog: [[0;32m OK [0m] Stopped Snappy daemon. Starting Snappy daemon... CompositorRunning: None CrashCounter: 1 Date: Fri Oct 5 20:36:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=) at assert.c:92 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101 ?? () Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX FORMULA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go
[Desktop-packages] [Bug 1860175] Re: Ability to rearrange applet icons by drag/drop.
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1860175 Title: Ability to rearrange applet icons by drag/drop. Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: 1) Ubuntu 19.10 2) Gnome 3.34.1 3) Ability to drag/drop applet icons to different places on the top bar. 4) Unable to drag/drop applet icons. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1860175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850651] Re: [SRU] Authentication constantly re-requested for Google
please revert my last change... I was searching if this was released for 16.04 and clicked by mistake. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1850651 Title: [SRU] Authentication constantly re-requested for Google Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Xenial: Fix Released Status in thunderbird source package in Bionic: Fix Committed Status in thunderbird source package in Disco: Fix Committed Status in thunderbird source package in Eoan: Fix Committed Status in thunderbird source package in Focal: Fix Released Bug description: [Impact] A recent server-side change with google e-mail accounts (gmail) means that thunderbird consistently fails to authenticate, prompting for the user's e-mail address and password over and over, without ever succeeding. This has been fixed upstream and is tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=1592407. [Test Case] In a clean environment, launch thunderbird and add an existing gmail account. Thunderbird should auto-detect all the relevant parameters, and then an external webview should pop up to prompt for your e-mail address (it's not auto-filled, that's a separate issue that's also known upstream) and your password. After filling this in and authorizing thunderbird to access your e-mails, your account should be set up and thunderbird should start fetching e-mails from your inbox. Instead it fails to authenticate and displays the authentication pop up again. [Regression Potential] Low, as this is an official upstream point release that addresses only this regression (see https://www.thunderbird.net/en-US/thunderbird/60.9.1/releasenotes/). The fix is minimal and self-contained (https://hg.mozilla.org/releases/comm-esr60/rev/56b6d1b50647143c25efe642b37b02f65f9c4343), if the bug is indeed confirmed to be fixed then it should be safe. [Original Bug Description] When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. I am using OAuth2 (so this ( https://support.mozilla.org/en- US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3444 F pulseaudio /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-03 (817 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090404 RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.9-0ubuntu4 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-05-22 (161 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430
[Desktop-packages] [Bug 1850651] Re: [SRU] Authentication constantly re-requested for Google
** Changed in: thunderbird (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1850651 Title: [SRU] Authentication constantly re-requested for Google Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Xenial: Fix Released Status in thunderbird source package in Bionic: Fix Committed Status in thunderbird source package in Disco: Fix Committed Status in thunderbird source package in Eoan: Fix Committed Status in thunderbird source package in Focal: Fix Released Bug description: [Impact] A recent server-side change with google e-mail accounts (gmail) means that thunderbird consistently fails to authenticate, prompting for the user's e-mail address and password over and over, without ever succeeding. This has been fixed upstream and is tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=1592407. [Test Case] In a clean environment, launch thunderbird and add an existing gmail account. Thunderbird should auto-detect all the relevant parameters, and then an external webview should pop up to prompt for your e-mail address (it's not auto-filled, that's a separate issue that's also known upstream) and your password. After filling this in and authorizing thunderbird to access your e-mails, your account should be set up and thunderbird should start fetching e-mails from your inbox. Instead it fails to authenticate and displays the authentication pop up again. [Regression Potential] Low, as this is an official upstream point release that addresses only this regression (see https://www.thunderbird.net/en-US/thunderbird/60.9.1/releasenotes/). The fix is minimal and self-contained (https://hg.mozilla.org/releases/comm-esr60/rev/56b6d1b50647143c25efe642b37b02f65f9c4343), if the bug is indeed confirmed to be fixed then it should be safe. [Original Bug Description] When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. I am using OAuth2 (so this ( https://support.mozilla.org/en- US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3444 F pulseaudio /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-03 (817 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090404 RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.9-0ubuntu4 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-05-22 (161 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8
[Desktop-packages] [Bug 1851936] Re: User profile won't load after upgrade - prompt to create new profile
Fixed with
https://bazaar.launchpad.net/~mozillateam/thunderbird/thunderbird.focal/revision/518.
** Changed in: thunderbird (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1851936
Title:
User profile won't load after upgrade - prompt to create new profile
Status in firefox package in Ubuntu:
Fix Released
Status in thunderbird package in Ubuntu:
Fix Committed
Bug description:
Did upgrade to focal fossa from standard Ubuntu 19.10. Existing
firefox profile won't load on starting, instead application wants new
default profile.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 70.0.1+build1-0ubuntu2
Uname: Linux 5.3.9-050309-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stefan 1861 F pulseaudio
/dev/snd/controlC0: stefan 1861 F pulseaudio
BuildID: 20191031000133
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 9 14:49:28 2019
DefaultProfileIncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
DefaultProfilePrefSources: prefs.js
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2019-05-02 (190 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
IpRoute:
default via 192.168.178.1 dev enp30s0 proto dhcp metric 100
169.254.0.0/16 dev enp30s0 scope link metric 1000
192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44
metric 100
MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 - LastVersion=70.0.1/20191031000133 (In use)
Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.80
dmi.board.name: AB350M-HDV
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851936] Re: User profile won't load after upgrade - prompt to create new profile
** Branch linked: lp:~mozillateam/thunderbird/thunderbird.xenial
** Branch linked: lp:~mozillateam/thunderbird/thunderbird.bionic
** Branch linked: lp:~mozillateam/thunderbird/thunderbird.disco
** Branch linked: lp:~mozillateam/thunderbird/thunderbird.eoan
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1851936
Title:
User profile won't load after upgrade - prompt to create new profile
Status in firefox package in Ubuntu:
Fix Released
Status in thunderbird package in Ubuntu:
Fix Committed
Bug description:
Did upgrade to focal fossa from standard Ubuntu 19.10. Existing
firefox profile won't load on starting, instead application wants new
default profile.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 70.0.1+build1-0ubuntu2
Uname: Linux 5.3.9-050309-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stefan 1861 F pulseaudio
/dev/snd/controlC0: stefan 1861 F pulseaudio
BuildID: 20191031000133
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 9 14:49:28 2019
DefaultProfileIncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
DefaultProfilePrefSources: prefs.js
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2019-05-02 (190 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
IpRoute:
default via 192.168.178.1 dev enp30s0 proto dhcp metric 100
169.254.0.0/16 dev enp30s0 scope link metric 1000
192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44
metric 100
MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 - LastVersion=70.0.1/20191031000133 (In use)
Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.80
dmi.board.name: AB350M-HDV
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851936] Re: User profile won't load after upgrade - prompt to create new profile
** Branch linked: lp:thunderbird
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1851936
Title:
User profile won't load after upgrade - prompt to create new profile
Status in firefox package in Ubuntu:
Fix Released
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
Did upgrade to focal fossa from standard Ubuntu 19.10. Existing
firefox profile won't load on starting, instead application wants new
default profile.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 70.0.1+build1-0ubuntu2
Uname: Linux 5.3.9-050309-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stefan 1861 F pulseaudio
/dev/snd/controlC0: stefan 1861 F pulseaudio
BuildID: 20191031000133
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 9 14:49:28 2019
DefaultProfileIncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
DefaultProfilePrefSources: prefs.js
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2019-05-02 (190 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
IpRoute:
default via 192.168.178.1 dev enp30s0 proto dhcp metric 100
169.254.0.0/16 dev enp30s0 scope link metric 1000
192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44
metric 100
MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 - LastVersion=70.0.1/20191031000133 (In use)
Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.80
dmi.board.name: AB350M-HDV
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808576] Re: gnome-control-center segfaults when unit bolt.service is masked
So... How about a fix! For Ubuntu 18.04.3 the bug happens when you inadvertently hit the gnome-control-center devices/thunderbolt section. gnome-control-center segfaults and will not restart! Fault: (gnome-control-center:8315): thunderbolt-cc-panel-WARNING **: 15:36:34.212: Could not create client: Error calling StartServiceByName for org.freedesktop.bolt: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit bolt.service is masked. Instead of waiting for a fix to this that happens upstream from Ubuntu18.04.3 you can just: sudo systemctl unmask bolt.service sudo systemctl stop bolt.service sudo systemctl start bolt.service The stop probably isn't necessary, but it doesn't hurt! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1808576 Title: gnome-control-center segfaults when unit bolt.service is masked Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center package in Fedora: Confirmed Bug description: I don't have any Thunderbolt devices so I masked the unused the bolt.service. This causes problem with gnome-control-center. Steps to reproduce: 1) launch gnome-control-center $ gnome-control-center 2) navigate to Thunderbolt section go to Devices, then Thunderbolt and close gnome-control-center 3) mask bold.service $ sudo systemctl stop bolt.service $ sudo systemctl mask bolt.service 4) re-launch gnome-control-center $ gnome-control-center (gnome-control-center:21859): thunderbolt-cc-panel-WARNING **: 14:04:53.423: Could not create client: Error calling StartServiceByName for org.freedesktop.bolt: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit bolt.service is masked. Segmentation fault (core dumped) Expected result: no segfault. Additional information: $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy gnome-control-center bolt gnome-control-center: Installed: 1:3.28.2-0ubuntu0.18.04.2 Candidate: 1:3.28.2-0ubuntu0.18.04.2 Version table: *** 1:3.28.2-0ubuntu0.18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.28.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages bolt: Installed: 0.5-0ubuntu0.18.04.1 Candidate: 0.5-0ubuntu0.18.04.1 Version table: *** 0.5-0ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 14 14:05:26 2018 InstallationDate: Installed on 2018-07-15 (152 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714) ProcEnviron: LANG=en_CA.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1808576/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860042] Re: openCL application gives error after update
** Description changed: My OpenCL program was working normally until a software update. The program prints out: ac_rtld error: !s->is_rx LLVM failed to upload shader when clEnqueueNDRangeKernel is called. I've downloaded the source for mesa and traced the problem to the - gallium radeon driver. + gallium radeon driver. The first error message is from + + mesa-19.2.1/src/amd/common/ac_rtld.c + + and the second error message is from + + mesa-19.2.1/src/gallium/drivers/radeonsi/si_shader.c + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libllvm9 1:9-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18 Uname: Linux 4.15.0-74-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 14:35:15 2020 InstallationDate: Installed on 2018-04-28 (628 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mesa-opencl-icd UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: My OpenCL program was working normally until a software update. The program prints out: ac_rtld error: !s->is_rx LLVM failed to upload shader when clEnqueueNDRangeKernel is called. I've downloaded the source for mesa and traced the problem to the gallium radeon driver. The first error message is from mesa-19.2.1/src/amd/common/ac_rtld.c and the second error message is from - mesa-19.2.1/src/gallium/drivers/radeonsi/si_shader.c - + mesa-19.2.1/src/gallium/drivers/radeonsi/si_compute.c ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libllvm9 1:9-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18 Uname: Linux 4.15.0-74-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 14:35:15 2020 InstallationDate: Installed on 2018-04-28 (628 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mesa-opencl-icd UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1860042 Title: openCL application gives error after update Status in mesa package in Ubuntu: New Bug description: My OpenCL program was working normally until a software update. The program prints out: ac_rtld error: !s->is_rx LLVM failed to upload shader when clEnqueueNDRangeKernel is called. I've downloaded the source for mesa and traced the problem to the gallium radeon driver. The first error message is from mesa-19.2.1/src/amd/common/ac_rtld.c and the second error message is from mesa-19.2.1/src/gallium/drivers/radeonsi/si_compute.c ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libllvm9 1:9-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18 Uname: Linux 4.15.0-74-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 14:35:15 2020 InstallationDate: Installed on 2018-04-28 (628 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mesa-opencl-icd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
After updating these packages with the proposed packages, it seems to resolve the issue: xserver-xorg-video-amdgpu-hwe-18.04:amd64 from 19.0.1-1~18.04.1 to 19.0.1-1ubuntu1~18.04.1 and xserver-xorg-video-ati-hwe-18.04:amd64 from 1:19.0.1-0ubuntu1~18.04.1 to 1:19.0.1-1ubuntu1~18.04.1 and xserver-xorg-video-radeon-hwe-18.04:amd64 from 1:19.0.1-0ubuntu1~18.04.1 to 1:19.0.1-1ubuntu1~18.04.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken Status in xserver-xorg-driver-ati: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu source package in Bionic: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati source package in Bionic: Invalid Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati source package in Eoan: Fix Released Status in xserver-xorg-video-ati package in Fedora: Fix Released Bug description: [Impact] Combo boxes are broken (cf screenshot) Tested in gnome-control-center and gtk3-demo. Tooltips are also garbage. [Test case] Install the updated package, test tooltips that they display fine. [Regression potential] This is a single commit backport from upstream, so there shouldn't be any regression potential To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1841718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1603430] Re: Firefox dropdowns in wrong location
* Ubuntu 18.04.3 LTS * Kernel 5.3.0-26-generic * Gnome 3.28.2 * Firefox 72.0.1 Confirmed this bug still exists. Fixed by disabling and re-enabling all add-ons that add an entry to this dropdown (aka right click context menu). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1603430 Title: Firefox dropdowns in wrong location Status in Linux Mint: New Status in cinnamon-desktop-environment package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: On Mint 17.3 Cinnamon 64bit. Steps to reproduce: * Do a fresh install. * Run mintupdate and update all packages. * Run firefox. * Start right clicking on the page to open the context menu. Resize the window and perhaps move it around the screen a couple of times. Right click some more. * Observer that, eventually, the context menu will start to appear in incorrect locations on the screen. The same also happens with the search bar, text fields and any other dropdown box. In the worst embodiment of the bug, the menu opens underneath the pointer and treats the release of the mouse button as a click, and so does things the user does not want to do. I believe the root cause is the following bug in GTK+ 3.10.8. Firefox switched over to using GTK+3 in version 46 which is when this bug appeared and has been there ever since. https://bugzilla.gnome.org/show_bug.cgi?id=758609 https://bugzilla.mozilla.org/show_bug.cgi?id=1022241 Mozilla aren't going to fix it because it's a GTK bug. GTK have already fixed it. But Mint 17.3 remains on GTK+ 3.10.8 which does not have the patch. Please roll out the patch for us 17.3 users who cannot upgrade. I can confirm that the problem is solved in Mint 18. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1603430/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
Crash on VirtualBox with `gstreamer1.0-vaapi` installed also is caused by: `gnome-books`, `gnome-contacts`, `gnome-control-center`, `gnome-documents`, `gnome-help`, `gnome-music`, `gnome-photo`, `gnome-sound-recorder`, `gnome-subtitles`. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1860163] Re: By default, group the LibreOffice icons into a folder called "LibreOffice"
Hi Clinton, thanks for the report. The Start Center, as corrado said, is indeed the current (and widely) accepted means of "grouping" LibreOffice into a single icon, so moving the applications into a folder labeled "LibreOffice" doesn't fit the project plans at this time, sorry. ** Changed in: libreoffice (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1860163 Title: By default, group the LibreOffice icons into a folder called "LibreOffice" Status in libreoffice package in Ubuntu: Won't Fix Bug description: 1) Ubuntu 19.10 2) 1:6.3.2-0ubuntu2 3) By default, the LibreOffice icons should be grouped into a folder called "LibreOffice". 4) By default, the LibreOffice icons were not grouped into a folder called "LibreOffice". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1860163/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860163] Re: By default, group the LibreOffice icons into a folder called "LibreOffice"
Much better: in /usr/share/applications you have an app named libreoffice-startcenter.desktop. Copy this to Your desktop for a unique icon capable to start all LibreOffice applications. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1860163 Title: By default, group the LibreOffice icons into a folder called "LibreOffice" Status in libreoffice package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 1:6.3.2-0ubuntu2 3) By default, the LibreOffice icons should be grouped into a folder called "LibreOffice". 4) By default, the LibreOffice icons were not grouped into a folder called "LibreOffice". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1860163/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737972] Re: Can not start httpd (apache), missing mod_dnssd.so
I have the same problem on 19.10 and can't find a fix after hours and hours of googling. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/1737972 Title: Can not start httpd (apache), missing mod_dnssd.so Status in gnome-user-share package in Ubuntu: Fix Released Status in smokeping package in Ubuntu: New Bug description: OS: Ubuntu 17.10 Version: 3.14.2-2ubuntu5 Steps to reproduce: 1. Open terminal and run: gnome-file-share-properties 2. Tick Share public files on network 3. In terminal see the error message: apache2: Syntax error on line 21 of /usr/share/gnome-user-share/dav_user_2.4.conf: Cannot load /usr/lib/apache2/modules//mod_dnssd.so into server: /usr/lib/apache2/modules/mod_dnssd.so: cannot open shared object file: No such file or directory Alternative steps to reproduce: 1. In terminal run gnome-control-center sharing 2. Enable File sharing 3. Same message appears To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/1737972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
** Attachment added: "crash file from Ubuntu MATE 20.04 LTS with all updates on start of Yelp" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1745345/+attachment/5321764/+files/_usr_lib_xorg_Xorg.0.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1745345] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1745345/+attachment/5321747/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1745345] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1745345/+attachment/5321746/+files/Xrandr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745345] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1745345/+attachment/5321741/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1745345] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1745345/+attachment/5321745/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1745345] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1745345/+attachment/5321744/+files/XorgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745345] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1745345/+attachment/5321740/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1745345] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1745345/+attachment/5321739/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
Hello Jean-Baptiste, or anyone else affected, Accepted xserver-xorg-video-ati-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-ati- hwe-18.04/1:19.0.1-1ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: xserver-xorg-video-ati-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic ** Changed in: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken Status in xserver-xorg-driver-ati: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu source package in Bionic: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati source package in Bionic: Invalid Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati source package in Eoan: Fix Released Status in xserver-xorg-video-ati package in Fedora: Fix Released Bug description: [Impact] Combo boxes are broken (cf screenshot) Tested in gnome-control-center and gtk3-demo. Tooltips are also garbage. [Test case] Install the updated package, test tooltips that they display fine. [Regression potential] This is a single commit backport from upstream, so there shouldn't be any regression potential To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1841718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841718] Please test proposed package
Hello Jean-Baptiste, or anyone else affected, Accepted xserver-xorg-video-amdgpu-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu- hwe-18.04/19.0.1-1ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken Status in xserver-xorg-driver-ati: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu source package in Bionic: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati source package in Bionic: Invalid Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati source package in Eoan: Fix Released Status in xserver-xorg-video-ati package in Fedora: Fix Released Bug description: [Impact] Combo boxes are broken (cf screenshot) Tested in gnome-control-center and gtk3-demo. Tooltips are also garbage. [Test case] Install the updated package, test tooltips that they display fine. [Regression potential] This is a single commit backport from upstream, so there shouldn't be any regression potential To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1841718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745345] LightdmDisplayLog.txt
apport information ** Attachment added: "LightdmDisplayLog.txt" https://bugs.launchpad.net/bugs/1745345/+attachment/5321734/+files/LightdmDisplayLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1745345] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1745345/+attachment/5321742/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1745345] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1745345/+attachment/5321733/+files/DpkgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745345] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1745345/+attachment/5321737/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745345] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1745345/+attachment/5321736/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-01-19 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200119) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=a7e811b1-6cbc-4d90-b1c9-8698611249e9 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Tags: focal ubuntu reproducible Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Tags added: apport-collected reproducible -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from
[Desktop-packages] [Bug 1745345] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1745345/+attachment/5321732/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1745345] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1745345/+attachment/5321743/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745345] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1745345/+attachment/5321738/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1745345] LightdmLog.txt
apport information ** Attachment added: "LightdmLog.txt" https://bugs.launchpad.net/bugs/1745345/+attachment/5321735/+files/LightdmLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1848522] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-amdgpu-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu- hwe-18.04/19.0.1-1ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1848522 Title: Backport packages for 18.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-9 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-9 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-9: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.2.x series, so there shouldn't be any regressions left at that point xserver: a new git snapshot (or maybe a point-release) xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848522] Re: Backport packages for 18.04.4 HWE stack
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-ati-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-ati- hwe-18.04/1:19.0.1-1ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: xserver-xorg-video-ati-hwe-18.04 (Ubuntu) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-ati-hwe-18.04 (Ubuntu) Status: New => Invalid ** Changed in: xserver-xorg-video-ati-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-needed verification-needed-bionic ** Also affects: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1848522 Title: Backport packages for 18.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-9 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-9 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-9: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.2.x series, so there shouldn't be any regressions left at that point xserver: a new git snapshot (or maybe a point-release) xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
I can confirm bug fix with new packages from ppa. After upgrade only two packages xserver-xorg-video-amdgpu-hwe-18.04:amd64 from 19.0.1-1~18.04.1 to 19.0.1-1ubuntu1~18.04.1 and xserver-xorg-video-ati-hwe-18.04:amd64 from 1:19.0.1-0ubuntu1~18.04.1 to 1:19.0.1-1ubuntu1~18.04.1 bug still reproduced. But after upgrade two more packages xserver-xorg-video-radeon-hwe-18.04:amd64 from 1:19.0.1-0ubuntu1~18.04.1 to 1:19.0.1-1ubuntu1~18.04.1 and error still reproduced from 2:1.19.6-1ubuntu4.3 to 2:1.19.6-1ubuntu4.4~ppa1 bug is gone! Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken Status in xserver-xorg-driver-ati: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu source package in Bionic: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-ati source package in Bionic: Invalid Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-ati source package in Eoan: Fix Released Status in xserver-xorg-video-ati package in Fedora: Fix Released Bug description: [Impact] Combo boxes are broken (cf screenshot) Tested in gnome-control-center and gtk3-demo. Tooltips are also garbage. [Test case] Install the updated package, test tooltips that they display fine. [Regression potential] This is a single commit backport from upstream, so there shouldn't be any regression potential To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1841718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gstreamer-vaapi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
For original problem with Ubuntu MATE Welcome one can use crash file from this link - https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1796437/+attachment/5319138/+files/_usr_lib_xorg_Xorg.0.crash . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
I need to recall that on QEMU/KVM (while using virt-manager the crashes occur with Cirrus, QXL, VGA video drivers, but does not occur with VMVGA video driver) and VirtualBox (tested all versions with default `vboxvideo` driver) the crash is caused by `gstreamer-vaapi` package (see https://packages.ubuntu.com/focal/gstreamer1.0-vaapi). It is a dependency of `ubuntu-restricted-addons` (see https://packages.ubuntu.com/focal/ubuntu-restricted-addons). So ubuntu-mate-welcome and for example Cheese with Yelp may be fixed by removing this package with ``` sudo apt-get purge gstreamer1.0-vaapi sudo apt-get autoremove --purge # to remove libgstreamer-plugins-bad1.0-0 (is not a problem) ``` So please carefully analyze the crash dumps for errors in `gstreamer1.0-vaapi` and fix this package. I'm not sure about the bug inside `xorg-server` codebase. ** Also affects: gstreamer-vaapi (Ubuntu) Importance: Undecided Status: New ** Tags removed: single-occurrence third-party-packages ** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP
[Desktop-packages] [Bug 1860316] Re: After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts
When i am run OS with 5.0.0-25-generic, I can select between 3 resolutions. Please, see attached screenshot. ** Attachment added: "2020-01-20-230621_1024x768_scrot.png" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1860316/+attachment/5321731/+files/2020-01-20-230621_1024x768_scrot.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1860316 Title: After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello! Yesterday, 01/19/2020, I updated my Lubuntu 18.04 lts. After restarting, the display resolution is only 640x480. I want to set a different resolution, but there are no other options. I restored Lubuntu from backup to Clonesilla. New OS work correctly, but after updating the problem appears again. Здравствуйте! Вчера, 19.01.2020, я обновил свою Lubuntu 18.04 lts. После перезапуска разрешение на дисплее только 640х480. Я хочу установить другое разрешение, но других вариантов нет. Я восстановил Lubuntu из резервной копии в Сlonesilla. Новые ОС работают корректно, но после обновления проблема появляется снова. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Jan 20 14:34:36 2020 InstallationDate: Installed on 2019-03-28 (297 days ago) InstallationMedia: Lubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1860316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
* xserver-common:all from 2:1.19.6-1ubuntu4.3 to 2:1.19.6-1ubuntu4.4~ppa1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken Status in xserver-xorg-driver-ati: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu source package in Bionic: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-ati source package in Bionic: Invalid Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-ati source package in Eoan: Fix Released Status in xserver-xorg-video-ati package in Fedora: Fix Released Bug description: [Impact] Combo boxes are broken (cf screenshot) Tested in gnome-control-center and gtk3-demo. Tooltips are also garbage. [Test case] Install the updated package, test tooltips that they display fine. [Regression potential] This is a single commit backport from upstream, so there shouldn't be any regression potential To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1841718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
Just tried the drivers (radeon) from ppa, works fine and the bug is gone. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken Status in xserver-xorg-driver-ati: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu source package in Bionic: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-ati source package in Bionic: Invalid Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-ati source package in Eoan: Fix Released Status in xserver-xorg-video-ati package in Fedora: Fix Released Bug description: [Impact] Combo boxes are broken (cf screenshot) Tested in gnome-control-center and gtk3-demo. Tooltips are also garbage. [Test case] Install the updated package, test tooltips that they display fine. [Regression potential] This is a single commit backport from upstream, so there shouldn't be any regression potential To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1841718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860235] Re: totem crashed with SIGSEGV in g_mount_spec_get()
** Changed in: gvfs Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1860235 Title: totem crashed with SIGSEGV in g_mount_spec_get() Status in gvfs: New Status in gvfs package in Ubuntu: New Status in totem package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/4ef67c07533ef05b6c12894767e604456aca3ace https://gitlab.gnome.org/GNOME/gvfs/issues/446 --- I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi PC (0x7ff6dc45dd09) ok source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (412 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1860235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860235] Re: totem crashed with SIGSEGV in g_mount_spec_get()
https://gitlab.gnome.org/GNOME/gvfs/issues/446 ** Also affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Description changed: https://errors.ubuntu.com/problem/4ef67c07533ef05b6c12894767e604456aca3ace - https://gitlab.gnome.org/GNOME/totem/issues/390 + https://gitlab.gnome.org/GNOME/gvfs/issues/446 --- I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi PC (0x7ff6dc45dd09) ok source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (412 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #446 https://gitlab.gnome.org/GNOME/gvfs/issues/446 ** No longer affects: totem ** Also affects: gvfs via https://gitlab.gnome.org/GNOME/gvfs/issues/446 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1860235 Title: totem crashed with SIGSEGV in g_mount_spec_get() Status in gvfs: Unknown Status in gvfs package in Ubuntu: New Status in totem package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/4ef67c07533ef05b6c12894767e604456aca3ace https://gitlab.gnome.org/GNOME/gvfs/issues/446 --- I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi PC (0x7ff6dc45dd09) ok source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (412 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1860235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860137] Re: Chromium-browser Snap is amnesiac
I enabled the flag, will report back. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1860137 Title: Chromium-browser Snap is amnesiac Status in chromium-browser package in Ubuntu: Incomplete Bug description: I'm using Ubuntu 19.10, latest Chromium(-browser) installed. The issue is that after the switch to snap-based Chromium it started forgetting my logged in sessions very very often. This is not isolated to one online service, I have to log back in to everything I use, including Chromium itself. It also forgets any "Remember this device" checkmarks. History, downloads or extensions however do not suffer from any data loss. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1860137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809685] Re: The evince application often freezes
** Changed in: evince Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1809685 Title: The evince application often freezes Status in Evince: New Status in evince package in Ubuntu: Confirmed Bug description: Hi! The evince application (pdf document viewer) often freezes. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 25 07:12:13 2018 InstallationDate: Installed on 2018-05-06 (232 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1809685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851936] Re: User profile won't load after upgrade - prompt to create new profile
Thanks Michał and Iain for the details. This is indeed the very same
problem that I recently fixed in the firefox packages, so I'll replicate
the fix for thunderbird.
In the meantime there are thunderbird packages in focal-proposed that
were rebuilt after the ones in eoan, so once they migrate to the release
pocket (which should happen soon as nothing is blocking) the issue will
go away.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1851936
Title:
User profile won't load after upgrade - prompt to create new profile
Status in firefox package in Ubuntu:
Fix Released
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
Did upgrade to focal fossa from standard Ubuntu 19.10. Existing
firefox profile won't load on starting, instead application wants new
default profile.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 70.0.1+build1-0ubuntu2
Uname: Linux 5.3.9-050309-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stefan 1861 F pulseaudio
/dev/snd/controlC0: stefan 1861 F pulseaudio
BuildID: 20191031000133
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 9 14:49:28 2019
DefaultProfileIncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
DefaultProfilePrefSources: prefs.js
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2019-05-02 (190 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
IpRoute:
default via 192.168.178.1 dev enp30s0 proto dhcp metric 100
169.254.0.0/16 dev enp30s0 scope link metric 1000
192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44
metric 100
MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 - LastVersion=70.0.1/20191031000133 (In use)
Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.80
dmi.board.name: AB350M-HDV
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
Sorry, this fell between the cracks.. I've pushed updated ati/amdgpu drivers to ppa:canonical-x/x-staging and to the SRU queue, feel free to test once they've been built ** Description changed: - Combo boxes are broken (cf screenshot) Tested in gnome-control-center - and gtk3-demo. + [Impact] + Combo boxes are broken (cf screenshot) Tested in gnome-control-center and gtk3-demo. Tooltips are also garbage. - ProblemType: Bug - DistroRelease: Ubuntu 19.10 - Package: gnome-shell 3.33.91-1ubuntu1 - ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 - Uname: Linux 5.2.0-13-generic x86_64 - NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair - ApportVersion: 2.20.11-0ubuntu7 - Architecture: amd64 - CurrentDesktop: ubuntu:GNOME - Date: Wed Aug 28 07:08:33 2019 - DisplayManager: gdm3 - InstallationDate: Installed on 2014-07-15 (1869 days ago) - InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) - RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 - SourcePackage: gnome-shell - UpgradeStatus: Upgraded to eoan on 2018-03-24 (521 days ago) + [Test case] + + Install the updated package, test tooltips that they display fine. + + [Regression potential] + + This is a single commit backport from upstream, so there shouldn't be + any regression potential -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken Status in xserver-xorg-driver-ati: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu source package in Bionic: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-ati source package in Bionic: Invalid Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-ati source package in Eoan: Fix Released Status in xserver-xorg-video-ati package in Fedora: Fix Released Bug description: [Impact] Combo boxes are broken (cf screenshot) Tested in gnome-control-center and gtk3-demo. Tooltips are also garbage. [Test case] Install the updated package, test tooltips that they display fine. [Regression potential] This is a single commit backport from upstream, so there shouldn't be any regression potential To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1841718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
** Also affects: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-ati-hwe-18.04 (Ubuntu) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-ati (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-amdgpu (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-ati-hwe-18.04 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-ati-hwe-18.04 (Ubuntu) Status: New => Invalid ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Bionic) Status: New => Invalid ** Changed in: xserver-xorg-video-ati (Ubuntu Bionic) Status: New => Invalid ** Changed in: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken Status in xserver-xorg-driver-ati: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu source package in Bionic: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-ati source package in Bionic: Invalid Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-ati source package in Eoan: Fix Released Status in xserver-xorg-video-ati package in Fedora: Fix Released Bug description: [Impact] Combo boxes are broken (cf screenshot) Tested in gnome-control-center and gtk3-demo. Tooltips are also garbage. [Test case] Install the updated package, test tooltips that they display fine. [Regression potential] This is a single commit backport from upstream, so there shouldn't be any regression potential To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1841718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1436555] Re: evince crashed with SIGSEGV in atk_object_notify_state_change()
** Changed in: evince (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1436555 Title: evince crashed with SIGSEGV in atk_object_notify_state_change() Status in Evince: Fix Released Status in evince package in Ubuntu: Fix Released Bug description: Just some random error message, I don't know what trigerred it. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: evince 3.14.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 25 13:41:32 2015 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2015-03-21 (4 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150320) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=839483f2-46c1-46c7-aa60-848b27c31a16 ro quiet splash vt.handoff=7 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f4e8eab7eaf : cmp%rax,(%rcx) PC (0x7f4e8eab7eaf) ok source "%rax" ok destination "(%rcx)" (0x680043) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: evince StacktraceTop: atk_object_notify_state_change () from /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0 ev_view_accessible_set_page_range () from /usr/lib/libevview3.so.3 ?? () from /usr/lib/libevview3.so.3 ?? () from /usr/lib/libevview3.so.3 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evince crashed with SIGSEGV in atk_object_notify_state_change() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1436555/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
I have the same error since the respective upgrade on Ubuntu 18.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken Status in xserver-xorg-driver-ati: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu source package in Bionic: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-ati source package in Bionic: Invalid Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-ati source package in Eoan: Fix Released Status in xserver-xorg-video-ati package in Fedora: Fix Released Bug description: Combo boxes are broken (cf screenshot) Tested in gnome-control-center and gtk3-demo. Tooltips are also garbage. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 07:08:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1869 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2018-03-24 (521 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1841718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809685] Re: The evince application often freezes
@William: I downloaded your pdf and checked: It does not reliably trigger this issue for me. But I experience the freeze issue almost daily, it happens randomly while zooming in documents. Sometimes I open a document and within the first zoom it freezes, sometimes I have to play around for minutes zooming and scrolling to trigger the issue. ** Changed in: evince (Ubuntu) Status: Expired => Confirmed ** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #1222 https://gitlab.gnome.org/GNOME/evince/issues/1222 ** Also affects: evince via https://gitlab.gnome.org/GNOME/evince/issues/1222 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1809685 Title: The evince application often freezes Status in Evince: Unknown Status in evince package in Ubuntu: Confirmed Bug description: Hi! The evince application (pdf document viewer) often freezes. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 25 07:12:13 2018 InstallationDate: Installed on 2018-05-06 (232 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1809685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860330] Re: After upgrading from Eoan to Focal, I receive the error: "A newer version of Thunderbird may have made changes to your profile which are no longer compatible with
*** This bug is a duplicate of bug 1851936 *** https://bugs.launchpad.net/bugs/1851936 A little more details in bug #1851936, which was originally a Firefox problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1860330 Title: After upgrading from Eoan to Focal, I receive the error: "A newer version of Thunderbird may have made changes to your profile which are no longer compatible with this older version. Use this profile only with that newer version, or create a new profile for this installation of Thunderbird. Creating a new profile requires setting up your accounts, calendars and add-ons again." Status in Mozilla Thunderbird: Unknown Status in thunderbird package in Ubuntu: New Bug description: I've only ever used the default Thunderbird that came packaged with Ubuntu. After upgrading from Eoan to Focal I receive the following popup error dialog: "A newer version of Thunderbird may have made changes to your profile which are no longer compatible with this older version. Use this profile only with that newer version, or create a new profile for this installation of Thunderbird. Creating a new profile requires setting up your accounts, calendars and add-ons again." The only options are "Create New Profile" and "Quit" with no option to continue using my old profile. I tried running thunderbird -ProfileManager to force my current default profile but it continued to give me the same error. I'm assuming this is a bug as it's a major inconvenience to have to reconfigure Thunderbird from scratch after an upgrade. Terminal shows: JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile directory. And after clicking Quit: JavaScript error: resource://gre/modules/AsyncShutdown.jsm, line 694: Error: Phase "xpcom-will-shutdown" is finished, it is too late to register completion condition "UserInteractionTimer 1 for document 7f645eb33000" See attached screenshot: focal-thunderbird-profile-bug.png Thanks, Sean. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:68.4.1+build1-0ubuntu1 ProcVersionSignature: User Name 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2592 F pulseaudio BuildID: 20200110122930 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Jan 20 14:43:03 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-06-06 (593 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 Profile1PrefSources: prefs.js Profile1Prefs: extensions.lastAppVersion: "68.4.1" (prefs.js) security.sandbox.plugin.tempDirSuffix: "18138464-d6cb-4282-a9d4-88ab6acfec88" (prefs.js) Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=68.4.1/20200110122930 Profile0 (Default) - LastVersion=68.4.1/20200110143530 (Out of date) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to focal on 2020-01-20 (0 days ago) dmi.bios.date: 09/05/2018 dmi.bios.vendor: System76 dmi.bios.version: 1.05.12-0 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp2 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnSystem76:bvr1.05.12-0:bd09/05/2018:svnSystem76:pnGalagoPro:pvrgalp2:rvnSystem76:rnGalagoPro:rvrgalp2:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Galago Pro dmi.product.sku: Not Applicable dmi.product.version:
[Desktop-packages] [Bug 1851936] Re: User profile won't load after upgrade - prompt to create new profile
Pasting this for SEO:
The error is:
"A newer version of Thunderbird may have made changes to your profile
which are no longer compatible with this older version. Use this profile
only with that newer version, or create a new profile for this
installation of Thunderbird. Creating a new profile requires setting up
your accounts, calendars and add-ons again."
I think running with --allow-downgrade is also a workaround, in addition
to the edit mentioned in comment #15
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1851936
Title:
User profile won't load after upgrade - prompt to create new profile
Status in firefox package in Ubuntu:
Fix Released
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
Did upgrade to focal fossa from standard Ubuntu 19.10. Existing
firefox profile won't load on starting, instead application wants new
default profile.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 70.0.1+build1-0ubuntu2
Uname: Linux 5.3.9-050309-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stefan 1861 F pulseaudio
/dev/snd/controlC0: stefan 1861 F pulseaudio
BuildID: 20191031000133
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 9 14:49:28 2019
DefaultProfileIncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
DefaultProfilePrefSources: prefs.js
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2019-05-02 (190 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
IpRoute:
default via 192.168.178.1 dev enp30s0 proto dhcp metric 100
169.254.0.0/16 dev enp30s0 scope link metric 1000
192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44
metric 100
MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 - LastVersion=70.0.1/20191031000133 (In use)
Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.80
dmi.board.name: AB350M-HDV
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860330] Re: After upgrading from Eoan to Focal, I receive the error: "A newer version of Thunderbird may have made changes to your profile which are no longer compatible with
*** This bug is a duplicate of bug 1851936 *** https://bugs.launchpad.net/bugs/1851936 Cheers. Saviq found this earlier, and Olivier (Thunderbird maintainer) suggested to use bug #1851936 to track the problem. Firefox had the same issue recently, and he fixed it there - probably the same fix needs to be applied to Thunderbird too. It's being worked on :-). I'll mark this bug as a duplicate. ** This bug has been marked a duplicate of bug 1851936 User profile won't load after upgrade - prompt to create new profile -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1860330 Title: After upgrading from Eoan to Focal, I receive the error: "A newer version of Thunderbird may have made changes to your profile which are no longer compatible with this older version. Use this profile only with that newer version, or create a new profile for this installation of Thunderbird. Creating a new profile requires setting up your accounts, calendars and add-ons again." Status in Mozilla Thunderbird: Unknown Status in thunderbird package in Ubuntu: New Bug description: I've only ever used the default Thunderbird that came packaged with Ubuntu. After upgrading from Eoan to Focal I receive the following popup error dialog: "A newer version of Thunderbird may have made changes to your profile which are no longer compatible with this older version. Use this profile only with that newer version, or create a new profile for this installation of Thunderbird. Creating a new profile requires setting up your accounts, calendars and add-ons again." The only options are "Create New Profile" and "Quit" with no option to continue using my old profile. I tried running thunderbird -ProfileManager to force my current default profile but it continued to give me the same error. I'm assuming this is a bug as it's a major inconvenience to have to reconfigure Thunderbird from scratch after an upgrade. Terminal shows: JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile directory. And after clicking Quit: JavaScript error: resource://gre/modules/AsyncShutdown.jsm, line 694: Error: Phase "xpcom-will-shutdown" is finished, it is too late to register completion condition "UserInteractionTimer 1 for document 7f645eb33000" See attached screenshot: focal-thunderbird-profile-bug.png Thanks, Sean. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:68.4.1+build1-0ubuntu1 ProcVersionSignature: User Name 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2592 F pulseaudio BuildID: 20200110122930 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Jan 20 14:43:03 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-06-06 (593 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 Profile1PrefSources: prefs.js Profile1Prefs: extensions.lastAppVersion: "68.4.1" (prefs.js) security.sandbox.plugin.tempDirSuffix: "18138464-d6cb-4282-a9d4-88ab6acfec88" (prefs.js) Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=68.4.1/20200110122930 Profile0 (Default) - LastVersion=68.4.1/20200110143530 (Out of date) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to focal on 2020-01-20 (0 days ago) dmi.bios.date: 09/05/2018 dmi.bios.vendor: System76 dmi.bios.version: 1.05.12-0 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp2 dmi.chassis.asset.tag: No Asset
[Desktop-packages] [Bug 1860330] Re: After upgrading from Eoan to Focal, I receive the error: "A newer version of Thunderbird may have made changes to your profile which are no longer compatible with
I see to have found a workaround: ubuntu@friendly:/usr/bin$ ./thunderbird -allow-downgrade Users shouldn't need to manually run this. Chatter from the below Web pages says: mahmacc said: > The instruction to change to the Thunderbird installation directory and then > run the command as ./thunderbird is not necessary for Linux users whose > paths are set up so the command above will work.) Matt said: > Hmm, and who has their path set correctly. My experience is that the more > people need help the less likely they are to even know what a path is. That > is certainly the case on Windows where very few appear to even have heard of > the path. It is still there and works like it always did. But the user base > of windows has no idea. References: * https://support.mozilla.org/en-US/questions/1276736 * https://thunderbirdtweaks.blogspot.com/2019/09/i-lost-my-profilemail-on-update-to.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1860330 Title: After upgrading from Eoan to Focal, I receive the error: "A newer version of Thunderbird may have made changes to your profile which are no longer compatible with this older version. Use this profile only with that newer version, or create a new profile for this installation of Thunderbird. Creating a new profile requires setting up your accounts, calendars and add-ons again." Status in Mozilla Thunderbird: Unknown Status in thunderbird package in Ubuntu: New Bug description: I've only ever used the default Thunderbird that came packaged with Ubuntu. After upgrading from Eoan to Focal I receive the following popup error dialog: "A newer version of Thunderbird may have made changes to your profile which are no longer compatible with this older version. Use this profile only with that newer version, or create a new profile for this installation of Thunderbird. Creating a new profile requires setting up your accounts, calendars and add-ons again." The only options are "Create New Profile" and "Quit" with no option to continue using my old profile. I tried running thunderbird -ProfileManager to force my current default profile but it continued to give me the same error. I'm assuming this is a bug as it's a major inconvenience to have to reconfigure Thunderbird from scratch after an upgrade. Terminal shows: JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile directory. And after clicking Quit: JavaScript error: resource://gre/modules/AsyncShutdown.jsm, line 694: Error: Phase "xpcom-will-shutdown" is finished, it is too late to register completion condition "UserInteractionTimer 1 for document 7f645eb33000" See attached screenshot: focal-thunderbird-profile-bug.png Thanks, Sean. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:68.4.1+build1-0ubuntu1 ProcVersionSignature: User Name 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2592 F pulseaudio BuildID: 20200110122930 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Jan 20 14:43:03 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-06-06 (593 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 Profile1PrefSources: prefs.js Profile1Prefs: extensions.lastAppVersion: "68.4.1" (prefs.js) security.sandbox.plugin.tempDirSuffix: "18138464-d6cb-4282-a9d4-88ab6acfec88" (prefs.js) Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=68.4.1/20200110122930 Profile0 (Default) -
[Desktop-packages] [Bug 1860330] [NEW] After upgrading from Eoan to Focal, I receive the error: "A newer version of Thunderbird may have made changes to your profile which are no longer compatible wit
Public bug reported: I've only ever used the default Thunderbird that came packaged with Ubuntu. After upgrading from Eoan to Focal I receive the following popup error dialog: "A newer version of Thunderbird may have made changes to your profile which are no longer compatible with this older version. Use this profile only with that newer version, or create a new profile for this installation of Thunderbird. Creating a new profile requires setting up your accounts, calendars and add-ons again." The only options are "Create New Profile" and "Quit" with no option to continue using my old profile. I tried running thunderbird -ProfileManager to force my current default profile but it continued to give me the same error. I'm assuming this is a bug as it's a major inconvenience to have to reconfigure Thunderbird from scratch after an upgrade. Terminal shows: JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile directory. And after clicking Quit: JavaScript error: resource://gre/modules/AsyncShutdown.jsm, line 694: Error: Phase "xpcom-will-shutdown" is finished, it is too late to register completion condition "UserInteractionTimer 1 for document 7f645eb33000" See attached screenshot: focal-thunderbird-profile-bug.png Thanks, Sean. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:68.4.1+build1-0ubuntu1 ProcVersionSignature: User Name 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2592 F pulseaudio BuildID: 20200110122930 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Jan 20 14:43:03 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-06-06 (593 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 Profile1PrefSources: prefs.js Profile1Prefs: extensions.lastAppVersion: "68.4.1" (prefs.js) security.sandbox.plugin.tempDirSuffix: "18138464-d6cb-4282-a9d4-88ab6acfec88" (prefs.js) Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=68.4.1/20200110122930 Profile0 (Default) - LastVersion=68.4.1/20200110143530 (Out of date) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to focal on 2020-01-20 (0 days ago) dmi.bios.date: 09/05/2018 dmi.bios.vendor: System76 dmi.bios.version: 1.05.12-0 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp2 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnSystem76:bvr1.05.12-0:bd09/05/2018:svnSystem76:pnGalagoPro:pvrgalp2:rvnSystem76:rnGalagoPro:rvrgalp2:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Galago Pro dmi.product.sku: Not Applicable dmi.product.version: galp2 dmi.sys.vendor: System76 ** Affects: thunderbird Importance: Unknown Status: Unknown ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "focal-thunderbird-profile-bug.png" https://bugs.launchpad.net/bugs/1860330/+attachment/5321703/+files/focal-thunderbird-profile-bug.png ** Bug watch added: Debian Bug tracker #946347 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946347 ** Also affects: thunderbird via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946347 Importance: Unknown Status: Unknown ** Description changed: I've only ever used the default Thunderbird that came packaged with Ubuntu. After upgrading from Eoan to Focal I receive the following popup error dialog: "A newer version of Thunderbird may have made changes to your profile which are no longer compatible with this older version. Use this profile only with that newer version, or
[Desktop-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
I have installed both xserver-xorg-video-amdgpu-hwe-18.04 and xserver- xorg-video-ati-hwe-18.04 $ aptitude show xserver-xorg-video-amdgpu-hwe-18.04 Package: xserver-xorg-video-amdgpu-hwe-18.04 Version: 19.0.1-1~18.04.1 New: yes State: installed Automatically installed: yes Priority: optional Section: x11 Maintainer: Ubuntu Developers Architecture: amd64 Uncompressed Size: 186 k Depends: libc6 (>= 2.17), libdrm-amdgpu1 (>= 2.4.73), libgbm1 (>= 10.2~0), libudev1 (>= 183), xorg-video-abi-24, xserver-xorg-core-hwe-18.04 (>= 2:1.18.99.901) Suggests: firmware-amd-graphics Conflicts: xserver-xorg-video-amdgpu, xserver-xorg-video-amdgpu:i386, xserver-xorg-video-amdgpu-hwe-18.04:i386 Replaces: xserver-xorg-video-amdgpu, xserver-xorg-video-amdgpu:i386 Provides: xorg-driver-video, xorg-renamed-package, xorg-renamed-package-hwe-18.04, xserver-xorg-video-amdgpu Description: X.Org X server -- AMDGPU display driver This package provides the 'amdgpu' driver for the AMD Radeon cards. The following chip families should be supported: Bonaire, Hawaii, Kaveri, Kabini Mullins, Iceland, Tonga, Carrizo, Fiji, Stoney. More information about X.Org can be found at: http://www.X.org> This package is built from the X.org xf86-video-amdgpu driver module. $ aptitude show xserver-xorg-video-ati-hwe-18.04 Package: xserver-xorg-video-ati-hwe-18.04 Version: 1:19.0.1-0ubuntu1~18.04.1 New: yes State: installed Automatically installed: yes Priority: optional Section: x11 Maintainer: Ubuntu Developers Architecture: amd64 Uncompressed Size: 46.1 k Depends: libc6 (>= 2.4), libpciaccess0, xorg-video-abi-24, xserver-xorg-core-hwe-18.04 (>= 2:1.18.99.901), xserver-xorg-video-radeon-hwe-18.04 Suggests: xserver-xorg-video-r128, xserver-xorg-video-mach64 Conflicts: xserver-xorg-video-ati, xserver-xorg-video-ati:i386, xserver-xorg-video-ati-hwe-18.04:i386 Replaces: xserver-xorg-video-ati, xserver-xorg-video-ati:i386 Provides: xorg-driver-video, xorg-renamed-package, xorg-renamed-package-hwe-18.04, xserver-xorg-video-ati Description: X.Org X server -- AMD/ATI display driver wrapper This package provides the 'ati' driver for the AMD/ATI Mach64, Rage128, Radeon, FireGL, FireMV, FirePro and FireStream series. This driver is actually a wrapper that loads one of the 'mach64', 'r128' or 'radeon' sub-drivers depending on the hardware. These sub-drivers are brought through package dependencies. Users of Rage, Mach, or Radeon boards may remove this package only if they use Driver "r128", "mach64", or "radeon" in /etc/X11/xorg.conf instead of relying on autodetection. More information about X.Org can be found at: https://www.X.org> This package is built from the X.org xf86-video-ati driver module. Homepage: https://wiki.freedesktop.org/xorg/RadeonFeature/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken Status in xserver-xorg-driver-ati: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Status in xserver-xorg-video-ati source package in Eoan: Fix Released Status in xserver-xorg-video-ati package in Fedora: Fix Released Bug description: Combo boxes are broken (cf screenshot) Tested in gnome-control-center and gtk3-demo. Tooltips are also garbage. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 07:08:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1869 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2018-03-24 (521 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1841718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
After downgrade packages, error is gone Old versions that correct works: libdrm2_2.4.97-1ubuntu1~18.04.1_amd64.deb libdrm2_2.4.97-1ubuntu1~18.04.1_i386.deb libdrm-amdgpu1_2.4.97-1ubuntu1~18.04.1_amd64.deb libdrm-amdgpu1_2.4.97-1ubuntu1~18.04.1_i386.deb libdrm-common_2.4.97-1ubuntu1~18.04.1_all.deb libdrm-dev_2.4.97-1ubuntu1~18.04.1_amd64.deb libdrm-intel1_2.4.97-1ubuntu1~18.04.1_amd64.deb libdrm-intel1_2.4.97-1ubuntu1~18.04.1_i386.deb libdrm-nouveau2_2.4.97-1ubuntu1~18.04.1_amd64.deb libdrm-nouveau2_2.4.97-1ubuntu1~18.04.1_i386.deb libdrm-radeon1_2.4.97-1ubuntu1~18.04.1_amd64.deb libdrm-radeon1_2.4.97-1ubuntu1~18.04.1_i386.deb libegl1-mesa_19.0.8-0ubuntu0~18.04.3_amd64.deb libegl1-mesa-dev_19.0.8-0ubuntu0~18.04.3_amd64.deb libegl-mesa0_19.0.8-0ubuntu0~18.04.3_amd64.deb libgbm1_19.0.8-0ubuntu0~18.04.3_amd64.deb libgl1-mesa-dev_19.0.8-0ubuntu0~18.04.3_amd64.deb libgl1-mesa-dri_19.0.8-0ubuntu0~18.04.3_amd64.deb libgl1-mesa-dri_19.0.8-0ubuntu0~18.04.3_i386.deb libgl1-mesa-glx_19.0.8-0ubuntu0~18.04.3_amd64.deb libgl1-mesa-glx_19.0.8-0ubuntu0~18.04.3_i386.deb libglapi-mesa_19.0.8-0ubuntu0~18.04.3_amd64.deb libglapi-mesa_19.0.8-0ubuntu0~18.04.3_i386.deb libgles2-mesa-dev_19.0.8-0ubuntu0~18.04.3_amd64.deb libglx-mesa0_19.0.8-0ubuntu0~18.04.3_amd64.deb libglx-mesa0_19.0.8-0ubuntu0~18.04.3_i386.deb libosmesa6_19.0.8-0ubuntu0~18.04.3_amd64.deb libosmesa6_19.0.8-0ubuntu0~18.04.3_i386.deb libwayland-egl1-mesa_19.0.8-0ubuntu0~18.04.3_amd64.deb libxatracker2_19.0.8-0ubuntu0~18.04.3_amd64.deb linux-generic-hwe-18.04_5.0.0.37.95_amd64.deb linux-headers-generic-hwe-18.04_5.0.0.37.95_amd64.deb linux-image-generic-hwe-18.04_5.0.0.37.95_amd64.deb mesa-common-dev_19.0.8-0ubuntu0~18.04.3_amd64.deb mesa-va-drivers_19.0.8-0ubuntu0~18.04.3_amd64.deb mesa-vdpau-drivers_19.0.8-0ubuntu0~18.04.3_amd64.deb xserver-xorg-core-hwe-18.04_1.20.4-1ubuntu3~18.04.1_amd64.deb xserver-xorg-legacy-hwe-18.04_1.20.4-1ubuntu3~18.04.1_amd64.deb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken Status in xserver-xorg-driver-ati: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Status in xserver-xorg-video-ati source package in Eoan: Fix Released Status in xserver-xorg-video-ati package in Fedora: Fix Released Bug description: Combo boxes are broken (cf screenshot) Tested in gnome-control-center and gtk3-demo. Tooltips are also garbage. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 07:08:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1869 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2018-03-24 (521 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1841718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796397] Re: DuckDuckGo search icon is blurry, low resolution
Fixed with https://bazaar.launchpad.net/~mozillateam/firefox/firefox.focal/revision/1349. ** Changed in: firefox (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1796397 Title: DuckDuckGo search icon is blurry, low resolution Status in firefox package in Ubuntu: Fix Committed Bug description: Firefox 62.0+build2-0ubuntu0.18.04.5 amd64 To reproduce: - Set search engine to DDG - Go to the new tab page. The DDG search icon is very low resolution and looks like it hasn't been updated with the new logo. Expected: Use the icon built into Firefox ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 62.0+build2-0ubuntu0.18.04.5 ProcVersionSignature: User Name 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1610 F pulseaudio /dev/snd/controlC0: ubuntu 1610 F pulseaudio BuildID: 20180913170256 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 15:46:16 2018 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-09-12 (23 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.224 metric 600 MostRecentCrashID: bp-5252eef0-71dd-4e49-8315-64d660180929 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile0 (Default) - LastVersion=62.0/20180913170256 (In use) Profile1 - LastVersion=62.0/20180913170346 (Out of date) RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-5252eef0-71dd-4e49-8315-64d660180929 bp-57477e57-d8dd-4ea9-ba66-270d80180929 bp-821e4afc-cb3c-4fe2-a7ba-586440180929 bp-8b4ffe0f-54ef-4969-b8fa-7d6bd0180929 UpgradeStatus: Upgraded to bionic on 2018-09-28 (6 days ago) dmi.bios.date: 07/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd07/09/2018:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3340 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1796397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851936] Re: User profile won't load after upgrade - prompt to create new profile
** Changed in: thunderbird (Ubuntu)
Status: New => Triaged
** Changed in: thunderbird (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: firefox (Ubuntu)
Importance: Undecided => High
** Changed in: thunderbird (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1851936
Title:
User profile won't load after upgrade - prompt to create new profile
Status in firefox package in Ubuntu:
Fix Released
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
Did upgrade to focal fossa from standard Ubuntu 19.10. Existing
firefox profile won't load on starting, instead application wants new
default profile.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 70.0.1+build1-0ubuntu2
Uname: Linux 5.3.9-050309-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stefan 1861 F pulseaudio
/dev/snd/controlC0: stefan 1861 F pulseaudio
BuildID: 20191031000133
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 9 14:49:28 2019
DefaultProfileIncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
DefaultProfilePrefSources: prefs.js
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2019-05-02 (190 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
IpRoute:
default via 192.168.178.1 dev enp30s0 proto dhcp metric 100
169.254.0.0/16 dev enp30s0 scope link metric 1000
192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44
metric 100
MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 - LastVersion=70.0.1/20191031000133 (In use)
Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.80
dmi.board.name: AB350M-HDV
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796397] Re: DuckDuckGo search icon is blurry, low resolution
** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: firefox (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1796397 Title: DuckDuckGo search icon is blurry, low resolution Status in firefox package in Ubuntu: Fix Committed Bug description: Firefox 62.0+build2-0ubuntu0.18.04.5 amd64 To reproduce: - Set search engine to DDG - Go to the new tab page. The DDG search icon is very low resolution and looks like it hasn't been updated with the new logo. Expected: Use the icon built into Firefox ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 62.0+build2-0ubuntu0.18.04.5 ProcVersionSignature: User Name 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1610 F pulseaudio /dev/snd/controlC0: ubuntu 1610 F pulseaudio BuildID: 20180913170256 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 15:46:16 2018 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-09-12 (23 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.224 metric 600 MostRecentCrashID: bp-5252eef0-71dd-4e49-8315-64d660180929 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile0 (Default) - LastVersion=62.0/20180913170256 (In use) Profile1 - LastVersion=62.0/20180913170346 (Out of date) RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-5252eef0-71dd-4e49-8315-64d660180929 bp-57477e57-d8dd-4ea9-ba66-270d80180929 bp-821e4afc-cb3c-4fe2-a7ba-586440180929 bp-8b4ffe0f-54ef-4969-b8fa-7d6bd0180929 UpgradeStatus: Upgraded to bionic on 2018-09-28 (6 days ago) dmi.bios.date: 07/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd07/09/2018:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3340 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1796397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851936] Re: User profile won't load after upgrade - prompt to create new profile
The same seems to happen with Thunderbird:
Przygotowywanie do rozpakowania pakietu
.../608-thunderbird_1%3a68.4.1+build1-0ubuntu1_amd64.deb ...
Rozpakowywanie pakietu thunderbird (1:68.4.1+build1-0ubuntu1) nad
(1:68.4.1+build1-0ubuntu0.19.10.1) ...
And then the dialog pops up.
The compatibility.ini file diff:
--- compatibility.ini.bup 2020-01-17 12:38:36.891947696 +0200
+++ compatibility.ini 2020-01-20 13:44:26.270351824 +0200
@@ -1,5 +1,5 @@
[Compatibility]
-LastVersion=68.4.1_20200110143530/20200110143530
+LastVersion=68.4.1_20200110122930/20200110122930
LastOSABI=Linux_x86_64-gcc3
LastPlatformDir=/usr/lib/thunderbird
LastAppDir=/usr/lib/thunderbird
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1851936
Title:
User profile won't load after upgrade - prompt to create new profile
Status in firefox package in Ubuntu:
Fix Released
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
Did upgrade to focal fossa from standard Ubuntu 19.10. Existing
firefox profile won't load on starting, instead application wants new
default profile.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 70.0.1+build1-0ubuntu2
Uname: Linux 5.3.9-050309-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stefan 1861 F pulseaudio
/dev/snd/controlC0: stefan 1861 F pulseaudio
BuildID: 20191031000133
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 9 14:49:28 2019
DefaultProfileIncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
DefaultProfilePrefSources: prefs.js
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2019-05-02 (190 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
IpRoute:
default via 192.168.178.1 dev enp30s0 proto dhcp metric 100
169.254.0.0/16 dev enp30s0 scope link metric 1000
192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44
metric 100
MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 - LastVersion=70.0.1/20191031000133 (In use)
Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.80
dmi.board.name: AB350M-HDV
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851936] Re: User profile won't load after upgrade - prompt to create new profile
Thunderbird appears to be similarly affected, according to some reports.
** Also affects: thunderbird (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1851936
Title:
User profile won't load after upgrade - prompt to create new profile
Status in firefox package in Ubuntu:
Fix Released
Status in thunderbird package in Ubuntu:
New
Bug description:
Did upgrade to focal fossa from standard Ubuntu 19.10. Existing
firefox profile won't load on starting, instead application wants new
default profile.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 70.0.1+build1-0ubuntu2
Uname: Linux 5.3.9-050309-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stefan 1861 F pulseaudio
/dev/snd/controlC0: stefan 1861 F pulseaudio
BuildID: 20191031000133
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 9 14:49:28 2019
DefaultProfileIncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
DefaultProfilePrefSources: prefs.js
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2019-05-02 (190 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
IpRoute:
default via 192.168.178.1 dev enp30s0 proto dhcp metric 100
169.254.0.0/16 dev enp30s0 scope link metric 1000
192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44
metric 100
MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 - LastVersion=70.0.1/20191031000133 (In use)
Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.80
dmi.board.name: AB350M-HDV
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1152137] Re: Pulseaudio won't start when home directory not owned by user
A fix for this has been merged upstream:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/134
I believe this should make it into the 14.0 release.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1152137
Title:
Pulseaudio won't start when home directory not owned by user
Status in pulseaudio package in Ubuntu:
Confirmed
Bug description:
I have an NFS mounted home directory on a dedicated fileserver which is
shared with Windows PCs via SMB.
The home directory is not owned by me. ACLs are set on it to allow me
full control of the contents but prevent me from changing its permissions.
This means any files or directories created in the home directory are owned
by me even though the top level is not.
Pulseaudio checks the home directory is owned by the user at startup and
exits if it isn't. This stops it running on my system.
I have recompiled pulseaudio without this check and it works fine.
Please either remove or modify the following startup check:
pulseaudio-1.1/src/pulsecore/src/pulsecore/core-util.c line 1415:
if (st.st_uid != getuid()) {
pa_log_error("Home directory %s not ours.", h);
errno = EACCES;
goto finish;
}
A better check would be for pulseaudio to try and create the files/folders it
needs and fail if it cannot.
I am using Ubuntu 12.04 and pulseaudio 1:1.1-0ubuntu15.2.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1152137/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796397] Re: DuckDuckGo search icon is blurry, low resolution
Not an upstream bug after all. I downloaded the latest release build, unpacked it in a clean VM and observed that the icon for DDG in the new tab page is reasonably high resolution, unlike the one in the Ubuntu builds. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1796397 Title: DuckDuckGo search icon is blurry, low resolution Status in firefox package in Ubuntu: Confirmed Bug description: Firefox 62.0+build2-0ubuntu0.18.04.5 amd64 To reproduce: - Set search engine to DDG - Go to the new tab page. The DDG search icon is very low resolution and looks like it hasn't been updated with the new logo. Expected: Use the icon built into Firefox ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 62.0+build2-0ubuntu0.18.04.5 ProcVersionSignature: User Name 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1610 F pulseaudio /dev/snd/controlC0: ubuntu 1610 F pulseaudio BuildID: 20180913170256 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 15:46:16 2018 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-09-12 (23 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.224 metric 600 MostRecentCrashID: bp-5252eef0-71dd-4e49-8315-64d660180929 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile0 (Default) - LastVersion=62.0/20180913170256 (In use) Profile1 - LastVersion=62.0/20180913170346 (Out of date) RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-5252eef0-71dd-4e49-8315-64d660180929 bp-57477e57-d8dd-4ea9-ba66-270d80180929 bp-821e4afc-cb3c-4fe2-a7ba-586440180929 bp-8b4ffe0f-54ef-4969-b8fa-7d6bd0180929 UpgradeStatus: Upgraded to bionic on 2018-09-28 (6 days ago) dmi.bios.date: 07/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd07/09/2018:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3340 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1796397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848841] Re: Chromium/Chrome/Electron look tiny in hidpi after gnome shell restart
** Summary changed:
- Chromium/Chrome looks tiny in hidpi after gnome shell restart
+ Chromium/Chrome/Electron look tiny in hidpi after gnome shell restart
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1848841
Title:
Chromium/Chrome/Electron look tiny in hidpi after gnome shell restart
Status in chromium-browser package in Ubuntu:
New
Bug description:
(upstream bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=1043494)
My screen is 3000x2000. I use a scaling factor of 2x. Today I upgraded
to 19.10 and chromium became a snap package. It launches at the right
scaling factor, but if I restart gnome shell (Alt-F2 r) it rescales to
1x (I believe) and everything becomes absurdly tiny. Restarting
chromium afterwards restores the right scaling factor.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wBRmIgTACobAQSlHRR4Asr8pFZPnicOT1UBAQEBAQEBAQEBAQEBAQEBuJi4oLDQPnAwIDUAJcQQAAAaAAAY/gBUSUFOTUEgWE0g/wBUTDEzOUdEWFAwMQAAAF8=
modes: 3000x2000
Date: Sat Oct 19 05:11:37 2019
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p2 ext4 331G 62G 255G 20% /
tmpfs tmpfs 7,8G 75M 7,7G 1% /dev/shm
/dev/nvme0n1p2 ext4 331G 62G 255G 20% /
InstallationDate: Installed on 2019-06-13 (127 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd
(Foxlink) HD Camera
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HUAWEI MACH-WX9
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic
root=UUID=08b323c0-f1a9-46a9-8d2c-694dff8193f6 ro quiet splash vt.handoff=7
Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.120
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
Snap.ChromiumVersion: Chromium 77.0.3865.120 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/28/2018
dmi.bios.vendor: HUAWEI
dmi.bios.version: 1.17
dmi.board.name: MACH-WX9-PCB
dmi.board.vendor: HUAWEI
dmi.board.version: M14
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M14
dmi.modalias:
dmi:bvnHUAWEI:bvr1.17:bd07/28/2018:svnHUAWEI:pnMACH-WX9:pvrM14:rvnHUAWEI:rnMACH-WX9-PCB:rvrM14:cvnHUAWEI:ct10:cvrM14:
dmi.product.family: HUAWEI MateBook X
dmi.product.name: MACH-WX9
dmi.product.sku: C128
dmi.product.version: M14
dmi.sys.vendor: HUAWEI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848841/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1859963] Re: Info package on Ubuntu Focal comes preinstalled with desktop file
Adding "NotShowIn=GNOME;" (without quotes) to /usr/share/applications/info.desktop could be sufficient. ** Also affects: hundredpapercuts Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1859963 Title: Info package on Ubuntu Focal comes preinstalled with desktop file Status in One Hundred Papercuts: New Status in texinfo package in Ubuntu: New Bug description: The "info" package that is preinstalled on Ubuntu Focal ships with a "info.desktop" file that adds a "TeXInfo" desktop launcher displayed among other apps. The launcher opens a terminal application that is confusing and user unfriendly for many users. Users that actually want to use info can do it using a terminal. Please, consider removing the desktop file or at least set it to not show among other apps. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1859963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858620] Re: [MIR] fonts-smc-gayathri
fonts-smc-gayathri 1.100-1 in focal: universe/misc -> main ** Changed in: fonts-smc-gayathri (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-smc-gayathri in Ubuntu. https://bugs.launchpad.net/bugs/1858620 Title: [MIR] fonts-smc-gayathri Status in fonts-smc-gayathri package in Ubuntu: Fix Released Bug description: * Availability Currently version builds fine and is in sync from Debian https://launchpad.net/ubuntu/+source/fonts-smc-gayathri/1.100-1 (it's a font and arch all so only amd64 build) * Rationale It has been added to the Malayalam fonts in Debian and is showing on component-mismatch now * Security No CVE/known security issue * Quality assurance - the desktop-packages team is subscribed to the package - the package is in sync with Debian - there are no open bugs on debian or launchpad * Dependendies The package has no depends * Standards compliance the package is using standard dh packaging and the current the standards-version, it is in sync from Debian * Maintainance The package is maintained in Debian by the fonts team, the desktop team is going to look at issues on the Ubuntu side if requires To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-smc-gayathri/+bug/1858620/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860316] Re: After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts
** Attachment added: "packages.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1860316/+attachment/5321702/+files/packages.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1860316 Title: After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello! Yesterday, 01/19/2020, I updated my Lubuntu 18.04 lts. After restarting, the display resolution is only 640x480. I want to set a different resolution, but there are no other options. I restored Lubuntu from backup to Clonesilla. New OS work correctly, but after updating the problem appears again. Здравствуйте! Вчера, 19.01.2020, я обновил свою Lubuntu 18.04 lts. После перезапуска разрешение на дисплее только 640х480. Я хочу установить другое разрешение, но других вариантов нет. Я восстановил Lubuntu из резервной копии в Сlonesilla. Новые ОС работают корректно, но после обновления проблема появляется снова. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Jan 20 14:34:36 2020 InstallationDate: Installed on 2019-03-28 (297 days ago) InstallationMedia: Lubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1860316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860316] Re: After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1860316/+attachment/5321700/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1860316 Title: After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello! Yesterday, 01/19/2020, I updated my Lubuntu 18.04 lts. After restarting, the display resolution is only 640x480. I want to set a different resolution, but there are no other options. I restored Lubuntu from backup to Clonesilla. New OS work correctly, but after updating the problem appears again. Здравствуйте! Вчера, 19.01.2020, я обновил свою Lubuntu 18.04 lts. После перезапуска разрешение на дисплее только 640х480. Я хочу установить другое разрешение, но других вариантов нет. Я восстановил Lubuntu из резервной копии в Сlonesilla. Новые ОС работают корректно, но после обновления проблема появляется снова. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Jan 20 14:34:36 2020 InstallationDate: Installed on 2019-03-28 (297 days ago) InstallationMedia: Lubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1860316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860316] Re: After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts
** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1860316/+attachment/5321701/+files/lspcik.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1860316 Title: After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello! Yesterday, 01/19/2020, I updated my Lubuntu 18.04 lts. After restarting, the display resolution is only 640x480. I want to set a different resolution, but there are no other options. I restored Lubuntu from backup to Clonesilla. New OS work correctly, but after updating the problem appears again. Здравствуйте! Вчера, 19.01.2020, я обновил свою Lubuntu 18.04 lts. После перезапуска разрешение на дисплее только 640х480. Я хочу установить другое разрешение, но других вариантов нет. Я восстановил Lubuntu из резервной копии в Сlonesilla. Новые ОС работают корректно, но после обновления проблема появляется снова. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Jan 20 14:34:36 2020 InstallationDate: Installed on 2019-03-28 (297 days ago) InstallationMedia: Lubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1860316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860316] Re: After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts
Yes, i am use nvidia-driver-390. 1. I am change this on "Nouveau dislpay driver". No result. 2. Then i am return on nvidia-driver-390 and load 5.0.0-27-generic kernel. No result. 3. I am return on 5.3.0-26-generic with nvidia-driver-390 and run commands. See attachment files. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1860316/+attachment/5321699/+files/dmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1860316 Title: After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello! Yesterday, 01/19/2020, I updated my Lubuntu 18.04 lts. After restarting, the display resolution is only 640x480. I want to set a different resolution, but there are no other options. I restored Lubuntu from backup to Clonesilla. New OS work correctly, but after updating the problem appears again. Здравствуйте! Вчера, 19.01.2020, я обновил свою Lubuntu 18.04 lts. После перезапуска разрешение на дисплее только 640х480. Я хочу установить другое разрешение, но других вариантов нет. Я восстановил Lubuntu из резервной копии в Сlonesilla. Новые ОС работают корректно, но после обновления проблема появляется снова. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Jan 20 14:34:36 2020 InstallationDate: Installed on 2019-03-28 (297 days ago) InstallationMedia: Lubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1860316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848841] Re: Chromium/Chrome looks tiny in hidpi after gnome shell restart
Thanks for the upstream bug Carlos.
I don't think it's a bug in the GNOME stack, given that you observe it only in
chrome/chromium and electron apps.
** Description changed:
+ (upstream bug:
+ https://bugs.chromium.org/p/chromium/issues/detail?id=1043494)
+
My screen is 3000x2000. I use a scaling factor of 2x. Today I upgraded
to 19.10 and chromium became a snap package. It launches at the right
scaling factor, but if I restart gnome shell (Alt-F2 r) it rescales to
1x (I believe) and everything becomes absurdly tiny. Restarting chromium
afterwards restores the right scaling factor.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
- enabled: disabled
- dpms: Off
- status: disconnected
- edid-base64:
- modes:
+ enabled: disabled
+ dpms: Off
+ status: disconnected
+ edid-base64:
+ modes:
DRM.card0-DP-2:
- enabled: disabled
- dpms: Off
- status: disconnected
- edid-base64:
- modes:
+ enabled: disabled
+ dpms: Off
+ status: disconnected
+ edid-base64:
+ modes:
DRM.card0-HDMI-A-1:
- enabled: disabled
- dpms: Off
- status: disconnected
- edid-base64:
- modes:
+ enabled: disabled
+ dpms: Off
+ status: disconnected
+ edid-base64:
+ modes:
DRM.card0-eDP-1:
- enabled: enabled
- dpms: On
- status: connected
- edid-base64:
AP///wBRmIgTACobAQSlHRR4Asr8pFZPnicOT1UBAQEBAQEBAQEBAQEBAQEBuJi4oLDQPnAwIDUAJcQQAAAaAAAY/gBUSUFOTUEgWE0g/wBUTDEzOUdEWFAwMQAAAF8=
- modes: 3000x2000
+ enabled: enabled
+ dpms: On
+ status: connected
+ edid-base64:
AP///wBRmIgTACobAQSlHRR4Asr8pFZPnicOT1UBAQEBAQEBAQEBAQEBAQEBuJi4oLDQPnAwIDUAJcQQAAAaAAAY/gBUSUFOTUEgWE0g/wBUTDEzOUdEWFAwMQAAAF8=
+ modes: 3000x2000
Date: Sat Oct 19 05:11:37 2019
DiskUsage:
- Filesystem Type Size Used Avail Use% Mounted on
- /dev/nvme0n1p2 ext4 331G 62G 255G 20% /
- tmpfs tmpfs 7,8G 75M 7,7G 1% /dev/shm
- /dev/nvme0n1p2 ext4 331G 62G 255G 20% /
+ Filesystem Type Size Used Avail Use% Mounted on
+ /dev/nvme0n1p2 ext4 331G 62G 255G 20% /
+ tmpfs tmpfs 7,8G 75M 7,7G 1% /dev/shm
+ /dev/nvme0n1p2 ext4 331G 62G 255G 20% /
InstallationDate: Installed on 2019-06-13 (127 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
- Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
- Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd
(Foxlink) HD Camera
- Bus 001 Device 002: ID 8087:0a2b Intel Corp.
- Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+ Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd
(Foxlink) HD Camera
+ Bus 001 Device 002: ID 8087:0a2b Intel Corp.
+ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HUAWEI MACH-WX9
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic
root=UUID=08b323c0-f1a9-46a9-8d2c-694dff8193f6 ro quiet splash vt.handoff=7
Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.120
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
Snap.ChromiumVersion: Chromium 77.0.3865.120 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/28/2018
dmi.bios.vendor: HUAWEI
dmi.bios.version: 1.17
dmi.board.name: MACH-WX9-PCB
dmi.board.vendor: HUAWEI
dmi.board.version: M14
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M14
dmi.modalias:
dmi:bvnHUAWEI:bvr1.17:bd07/28/2018:svnHUAWEI:pnMACH-WX9:pvrM14:rvnHUAWEI:rnMACH-WX9-PCB:rvrM14:cvnHUAWEI:ct10:cvrM14:
dmi.product.family: HUAWEI MateBook X
dmi.product.name: MACH-WX9
dmi.product.sku: C128
dmi.product.version: M14
dmi.sys.vendor: HUAWEI
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1848841
Title:
Chromium/Chrome looks tiny in hidpi after gnome shell restart
Status in chromium-browser package in Ubuntu:
New
Bug description:
(upstream bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=1043494)
My screen is 3000x2000. I use a scaling factor of 2x. Today I upgraded
to 19.10 and chromium became a snap package. It launches at the right
scaling factor, but if I restart gnome shell (Alt-F2 r) it rescales to
1x (I believe) and everything becomes absurdly tiny. Restarting
chromium afterwards restores the right scaling factor.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
[Desktop-packages] [Bug 1860137] Re: Chromium-browser Snap is amnesiac
It sounds like this might be a symptom of bug #1616650 (although the claim that history isn't affected would go against this hypothesis). Could you try enabling the experimental refresh-app-awareness flag, restart chromium, use it for a few days and comment back here whether the problem persists? snap set core experimental.refresh-app-awareness=true Thanks! ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1860137 Title: Chromium-browser Snap is amnesiac Status in chromium-browser package in Ubuntu: Incomplete Bug description: I'm using Ubuntu 19.10, latest Chromium(-browser) installed. The issue is that after the switch to snap-based Chromium it started forgetting my logged in sessions very very often. This is not isolated to one online service, I have to log back in to everything I use, including Chromium itself. It also forgets any "Remember this device" checkmarks. History, downloads or extensions however do not suffer from any data loss. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1860137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1859610] Re: python-gi/arm64 segfaults with the focal-proposed libffi version
so this apparently needs re-testing with appropriate triggers, or maybe tightened dependencies on some packages. ** Also affects: pygobject (Ubuntu) Importance: Undecided Status: New ** Changed in: libffi (Ubuntu Focal) Status: Incomplete => Fix Committed ** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1859610 Title: python-gi/arm64 segfaults with the focal-proposed libffi version Status in libffi package in Ubuntu: Fix Committed Status in pygobject package in Ubuntu: New Status in libffi source package in Focal: Fix Committed Status in pygobject source package in Focal: New Bug description: Testcase, on focal/arm64 $ sudo apt install python3-goocalendar $ python3 -c "import goocalendar ; print(goocalendar.__version__)" -> works fine install the python3-gi package from focal-proposed it segfaults in libffi Program received signal SIGSEGV, Segmentation fault. 0x in ?? () (gdb) bt #0 0x in ?? () #1 0xf7390ff8 in ffi_call_SYSV () at ../src/aarch64/sysv.S:114 #2 0xf7390634 in ffi_call_int (cif=0xa12d78, fn=, orig_rvalue=, avalue=0x0, closure=) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1859610/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860317] Re: package libreoffice-math 1:6.3.2-0ubuntu2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
Please could you try `sudo apt clean` then retry the upgrade. ** Changed in: libreoffice (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1860317 Title: package libreoffice-math 1:6.3.2-0ubuntu2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 Status in libreoffice package in Ubuntu: Incomplete Bug description: This issue happened after I installed Ubuntu 19.10. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libreoffice-math 1:6.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Mon Jan 20 16:32:19 2020 DuplicateSignature: package:libreoffice-math:1:6.3.2-0ubuntu2 Unpacking python3-uno (1:6.3.4-0ubuntu0.19.10.1) over (1:6.3.2-0ubuntu2) ... dpkg-deb: error: '/tmp/apt-dpkg-install-6hbkh8/095-libreoffice-math_1%3a6.3.4-0ubuntu0.19.10.1_amd64.deb' is not a Debian format archive dpkg: error processing archive /tmp/apt-dpkg-install-6hbkh8/095-libreoffice-math_1%3a6.3.4-0ubuntu0.19.10.1_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 2 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 InstallationDate: Installed on 2020-01-20 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: libreoffice Title: package libreoffice-math 1:6.3.2-0ubuntu2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1860317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
rockbomber, what's the version of xserver-xorg-video-ati-hwe-18.04 or -amdgpu-hwe-18.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken Status in xserver-xorg-driver-ati: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Status in xserver-xorg-video-ati source package in Eoan: Fix Released Status in xserver-xorg-video-ati package in Fedora: Fix Released Bug description: Combo boxes are broken (cf screenshot) Tested in gnome-control-center and gtk3-demo. Tooltips are also garbage. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 07:08:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1869 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2018-03-24 (521 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1841718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857787] Re: Bluetooth cannot be turned on once turned off
Thank you for your bug report. Can you include a screenshot showing the wrong status and a 'journalctl -b 0' log after getting the problem? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1857787 Title: Bluetooth cannot be turned on once turned off Status in gnome-bluetooth package in Ubuntu: New Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Given that Bluetooth is disabled, And I want to enable the bluetooth, When I open the Bluetooth tab in Settings And I press the button, Then the button background turns green but the handle does not move (State 1- Bug 1) Being at State 1, When I move to another tab, And I come back to the "Bluetooth" tab Then the Bluetooth is enabled and I can choose a bluetooth device. (State 2) Being at State 2, When I disable the Bluetooth And I start the process from the beginning Then I cannot re-enable the Bluetooth Ubuntu version: Ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-bluetooth 3.34.0-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 29 01:12:53 2019 InstallationDate: Installed on 2019-06-22 (189 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to eoan on 2019-11-01 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1857787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860316] Re: After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts
Thanks for the bug reports. Sorry you're having trouble getting the right attachments, I can't see why... My first guess here is that maybe you're using Nvidia and the nvidia-390 driver? If so then please try booting an older kernel like 5.0 and see bug 1851162. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1860316 Title: After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello! Yesterday, 01/19/2020, I updated my Lubuntu 18.04 lts. After restarting, the display resolution is only 640x480. I want to set a different resolution, but there are no other options. I restored Lubuntu from backup to Clonesilla. New OS work correctly, but after updating the problem appears again. Здравствуйте! Вчера, 19.01.2020, я обновил свою Lubuntu 18.04 lts. После перезапуска разрешение на дисплее только 640х480. Я хочу установить другое разрешение, но других вариантов нет. Я восстановил Lubuntu из резервной копии в Сlonesilla. Новые ОС работают корректно, но после обновления проблема появляется снова. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Jan 20 14:34:36 2020 InstallationDate: Installed on 2019-03-28 (297 days ago) InstallationMedia: Lubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1860316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
